[AccessD] Changing Default Printer

This is a work in progress so I don't have precise answers yet.  But, the
plan is to have the user install whatever PDF printer they like .  In the
control panel of the Automated Email System there's a combo box with all of
the installed printers.  They pick their PDF printer and it's saved in a
local options table.  So they'll be providing their own PDF printer.  Which
might finesse the problem you had.

Rocky





 	
	

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Wednesday, August 08, 2007 10:23 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Changing Default Printer

Um ... Is this PDF printer something you provide in your app?  We've found
that we needed to include an installer for our clients to reinstall their
PDF printer when it went sideways, and we ran into problems if a full
version of Adobe Acrobat was installed on the same machine.

Charlotte Foust 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at
Beach Access Software
Sent: Wednesday, August 08, 2007 9:09 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Changing Default Printer

Well, that won't be a problem for my app.  Al I want to do it have the user
switch to a PDF printer for reports which will then be attached to emails.


Rocky



 	
	

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Wednesday, August 08, 2007 8:52 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Changing Default Printer

OY!! After all this time I don't recall.  I know I wrote printer object
based code to replace all our old code to set page size properly and then
after testing it a bit, I threw it out and went back to the original code.
I don't think it was a problem with selecting the printer, it was trying to
manipulate the page settings that gave us problems.

Charlotte Foust 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at
Beach Access Software
Sent: Wednesday, August 08, 2007 8:45 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Changing Default Printer

Uh-oh.  What problems did you have with the Printer object?  Is that the
same as using Application.Printer?

Rocky
 




 	
	

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Wednesday, August 08, 2007 8:08 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Changing Default Printer

A2002 was the first version to have a printer object.  I have to tell you,
though, that we tried it and went back to API calls as more consistent and
reliable.

Charlotte Foust 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at
Beach Access Software
Sent: Wednesday, August 08, 2007 7:21 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Changing Default Printer

What version of Access has that Printer object?  And that code would go into
the report in the load or open event?  The code I found that I posted
yesterday works in A2K3, it's real short, but does it at the OS level, which
is probably more sketchy than doing it inside Access itself. What to you
think?

Rocky