I'd like to add this functionality into my project, but it seems impossible.
It's a split database (DB_FRONT.mdb & DB_DATA.mdb)
1. End-user printer selection:
There are 3 categories of reports. I would like the user to be able to view a list of printers, and select a printer for each category of report.
Example (from a form):
All full page reports go to the laser printer (Networked)
All receipts to receipt printer (LPT2)
All labels to label printer (LPT3)
Of course, I can set this up myself from each report's design view, but every machine has a different printer configuration.
Also, I can set all reports to print to default printer and then instruct the user to switch default printer from Windows, but this is inelegant also.
2. End-user compact back-end database
From a menu selection in DB_FRONT.mdb I want the user to be able to compact DB_DATA.mdb
This will also allow backing-up the back-end database during compacting.
I've studied the Access97 Developer's Handbook, MSDN, and help at great length for this, but can't find what I need.
Please let me know if I need to clarify what I am trying to achive, or if I am trying to do something that Access simply will not allow.
It's a split database (DB_FRONT.mdb & DB_DATA.mdb)
1. End-user printer selection:
There are 3 categories of reports. I would like the user to be able to view a list of printers, and select a printer for each category of report.
Example (from a form):
All full page reports go to the laser printer (Networked)
All receipts to receipt printer (LPT2)
All labels to label printer (LPT3)
Of course, I can set this up myself from each report's design view, but every machine has a different printer configuration.
Also, I can set all reports to print to default printer and then instruct the user to switch default printer from Windows, but this is inelegant also.
2. End-user compact back-end database
From a menu selection in DB_FRONT.mdb I want the user to be able to compact DB_DATA.mdb
This will also allow backing-up the back-end database during compacting.
I've studied the Access97 Developer's Handbook, MSDN, and help at great length for this, but can't find what I need.
Please let me know if I need to clarify what I am trying to achive, or if I am trying to do something that Access simply will not allow.