Darryl Collins
Darryl.Collins at coles.com.au
Sat Aug 9 19:12:47 CDT 2008
Hi Mark, regardless of your printer issue I would implement option 2 anyway. If you are using an Access database over a LAN (or WAN) and with multiple users you really want to split the db into FE and BE. If this is also going to fix your printer issue as well than that is great, but either way seriously consider it. cheeres Darryl -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Mark Breen Sent: Saturday, 9 August 2008 12:32 AM To: Access Developers discussion and problem solving Subject: [AccessD] Selecting a Printer, and dealing with Paper Types Hello All, Hope summer is treating you all well. In Ireland, we currently have rain, rain, and a little more rain. I have an Access 2000 / 2002 / 2003 app that prints to a big HP printer with four paper trays. In the application, I call multiple reports in a sequence, that eventually gives me a 27 page doc, printed on various paper trays. To facilitate this, I go into Page Setup, select specific Printer and then select the paper type. I then save the report and it remembers the preferred paper type for that printer. So far so good. I recently tried to give access to the mdb file from other machines on the lan, but I find that when I open the reports, it has reverted to using the default printer. I initially thought that what I needed was a network based printer, that would be common to all machines, so I installed the driver on a server, and shared it out and then changed the specific printer in Page Setup to point to the Network based printer. But when I went to another PC on the Lan, and opened the reports, they were switching again to the default printer. In summary, it looks like I have to programatically tell Access which printer to use. In my case, I only have 5-6 pc's to deal with, so I do not need a 1000 user solution to this problem. My choices are 1) tell the customer that they can only print from one machine 2) Split the db in to FE and BE and save the FE on each workstation and that should avoid the problem occuring. 3) build a programatic solution, but from reading emails in AccessD, it may not be so easy to get reliable. Any thoughts on this ? thanks Mark -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.