Surely there is someone else out there who has done this!
MS Access app on Server 2003 with Office 2002 to SQL Server 2000.
I have numerous files (.doc, .snp, .pdf, .xls) stored on my server
that are associated with records in my database--note that files exist
OUTSIDE of the database. Occasionally my user needs to print all files
associated with a certain record and in a standard client/server
environment I do that with code, specifically with an API call using
ShellExecute and the 'Print' verb.
However, for my users that have been moved to Terminal Server, batch
printing files from code is not working. It seems that the problem is
that TS doesn't know which printer to use when I make the API call.
Note that all files will print just fine if the user opens up one file
in the native app and asks the app to print it so this is not an issue
of printer drivers, etc. However, some apps, e.g. Acrobat Reader, will
always ask the user to specify a printer even under these conditions.
My tests with Shell and the 'PrintTo' verb as well as hacking some
command line strings together and running them from VBA have not
turned up any viable results. Command line stuff that will do the job
from my PC fail when run on TS.
So, I'm looking for a way to send files for printing and specify what
printer to use or in some way let TS know what user need the prints so
it can find the user's default printer. Additionally, I'm looking for
how to specify a user's printer to TS.
Any suggestions?
Thanks for the help!
|
Similar Threads
