Gustav Brock
Gustav at cactus.dk
Wed Feb 20 11:32:21 CST 2008
Hi Jim We've seen similar issues, though with Access 97, when an app runs in WinXP. I think we had some threads about this years ago. Our findings have been, that if the printer settings in the Registry of Windows are not _completely_ identical - which they never are between two sites - Access will, when the app launches the first time at the client, "readjust to the "new" environment and possibly ruin the delicate printer settings of your reports. This did not happen when OS was WinNT or 98. After much trial and error we gave up and installed at the client a remote control (RealVNC or just VNC) on a superuser's workstation and a full version of Access. Whenever a revised version of the app was deployed, we installed it on this machine only, opened one by one all reports in design mode, readjusted printer settings as needed, and saved. Then that copy of the front end mdb file was saved as a "site master" and copied to the remaining workstations. Not very fancy but it works. Note too, that even if the physical printer is the same, printer driver or printer settings (say, Postscript or PCL) and ports are rarely identical. /gustav >>> jimdettman at verizon.net 20-02-2008 17:54 >>> Dan, Not all. Most are set to "Use Default", but even in the cases where a report was set to a specific printer, the same thing has happened. It was first noticed in a label program. 4 x 6 labels created for landscape started printing out in portrait mode. This was even with the exact same printer and driver setup on the new box (there was no warning that the report was being formatted for another printer when opened). I also tried running some code using the application.printer object to grab defaults and then update the reports. Got a lot of weird errors out of that (ie. could not set margins without an error, device name in the report would end up blank, etc). process and have resorted to changing everything by hand. JimD. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters Sent: Wednesday, February 20, 2008 11:07 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Print settings problems with 2003. Jim, Were the reports previously set to use a specific printer, which no longer exists? Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman Sent: Wednesday, February 20, 2008 9:49 AM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Print settings problems with 2003. All, Just moved a client from Phoenix to Ohio and in the process am now running their apps under Access 2003, SP3. Originally they were running under A2000. I left all the databases in 2000 format. I'm seeing a variety of printing issues, but it boils down to margins and orientation are getting messed up when a report opens. I've already turned off Auto Correct and that didn't fix it. Anyone have any ideas? This is rather urgent as things are starting to come to a standstill and it's turning into a major mess. Thanks, Jim.