Portland Access User Group
Portland Access User Group Conference September 28-30, 2019
The PAUG Database Designer International conference brings together a wide range of Access developers, consultants, power users and Access enthusiasts. This marks the 21st anniversary of the conference. We will once again be returning to the peaceful and natural surroundings of the Conference Center at Silver Falls State Park, which lends itself to a climate that fosters learning, creativity, and socializing.
Tuesday, April 20, 2010
by A.D. Tejpal
This sample db demonstrates printing of multiple reports with dynamic assignment of caption via report's open event. The user can alter the sequence of printing as desired, by moving the report names up or down. Out of available reports, those required to be included in sequential printing are selected by ticking the check box adjacent to report name.
It is observed that if a report is printed directly by opening in normal view, the caption assigned programmatically in report's open event does not get properly captured in the print queue of the printer. This is explained by the fact that caption of active window tends to get captured for the above purpose. Depending upon the local set up, direct opening of report might not project its window presence adequately. For absolute certainty, it is therefore necessary that the report is first opened in preview mode, followed by PrintOut and Close actions.
It would be interesting to note that you can't get away by opting for preview in hidden mode. In that case, you might even end up with the caption of the calling form getting depicted in print queue. The defining requirement is that the report should be the visible active window (even if for a very brief duration) when requisite information is getting passed to the printer.
Time delay (in clock cycles) as included between various stages (e.g. opening in preview mode, print out and closing), as a measure of abundant precaution, is meant for stabilization between one step and the next.
You can find the sample here:
Monday, April 12, 2010
I say this, because a number of features that were introduced in 2007 aren't really useful until 2010. For instance, I consider multiple-value fields (for tables) and Layout View (for forms) to be either useless or down-right dangerous in 2007. However, with the introduction of Web Databases in 2010, both of these features become necessary. I would never use either in a client database (that is, one that opens and runs in Access on the desktop) but I would use these in a database that runs in a web browser.
Access 2007 introduced a new type of template, that is more useful than those in earlier versions, but 2010 introduces another new type of template called Application Parts, which is meant to incorporate generalized functions into an existing database application. To my mind, that's more useful than the kind of template that creates an entire application from scratch.
The result is that many Access 2007 features were really aimed at 2010. Once 2010 comes out, I expect I'll use that exclusively.
Friday, April 2, 2010
If you click the scroll bar or press PgDn to move down the list, it moves one page worth, then keeps moving a few more times over several seconds. This happens only in the "Details View" or "Icon View" of the Nav Pane.
There is a hotfix available here: http://support.microsoft.com/kb/973405.