Ms Access via Terminal Services on Wind Server 2003

[Ken]

I work on a long standing application, the customer has gone to server 2003
and wishes to use the access program via Terminal Services. My problem is
there are many emails automatically sent using PDF format. This is not
wanting to work on server 2003. It seems it will not allow the pdfwriter to
install.

Please advise if you know best way to work around this or to completely redo
application if necessary.

Mr Kallal says the application should work well via terminal services.

Thank you

 

[a a r o n . k e m p f]

Terminal Services is not a good solution-- using Access Data Projects
over a network, IMHO is a much more robust system.

That way- if you had 20 people sending PDFs all day long-- they
couldn't choke up a single machine. Just the bandwidth alone- on a
clunky PDF - might choke up a terminal services machine with a single
user.

Or if you wanted to send plain text or html emails- you could do that
directly with SQL Server; and you would have a much more robust
system.

It is _ALWAYS_ more secure to send email from one machine instead of
12. Any way that you look at it.

With SQL Server Reporting Services- for example; it would be quite
easy to send out hundreds if not thousands of PDFs per day. I should
know; I've used it like that.

-Aaron

 

[david]

You need to ask this question in a Terminal Services group.

My guess would be that your users don't have permission to
install printers on the server, or perhaps don't have permisson
to install new printers on the server. You should get an Admin
to install pdfwriter first, so that you know that the driver files
are available on the server. You may also want to try to install
pdfwriter as a network printer (so that it runs on the server)

(david)

 

[Tony Toews [MVP]]

Terminal Services is not a good solution--

Absolute rubbish. Terminal Services works just fine.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Toews [MVP]]

I work on a long standing application, the customer has gone to server 2003
and wishes to use the access program via Terminal Services. My problem is
there are many emails automatically sent using PDF format. This is not
wanting to work on server 2003. It seems it will not allow the pdfwriter to
install.

I would suggest using a bit of code and Stephen Lebans solution.

A2000ReportToPDF is an Access 2000 database containing a function to
convert Reports and Snapshot files to PDF documents. No PDF Printer
driver is required.
http://www.lebans.com/reporttopdf.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Toews [MVP]]

It seems it will not allow the pdfwriter to install.

BTW what specific PDF writer software won't install on Windows 2003
Server?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Ken]

Tony , thank you for your comments.
Now I am going to go into the server, and see what errors are being thrown,
to date I have been working on basis of report from our network programmer,
who says the the server throws error and won't load pdfwriter. The client
has Adobe 4 full on the machine and has for a long time. they dont want to
upgrade tha. To date it has always worked perfectly with the Access
application. I will run some tests, and read Lebans solution and try it and
then come back here with update later today 4/16/2008. Your help and insight
is so greatly appreciated. Your blog will be next on my list.

Ken

 

[a a r o n . k e m p f]

It's a _CON_.

SQL Server is cheaper than terminal services.

It works _FASTER_ because people can use local and server-based
resources.

Terminal Services- for runing MS Access- is not reccomended.

If you want to support VPN, WAN and Wireless-- then just move to ADP /
SQL Server.

MDB doesn't work across these networks-- these kids blame the networks
not the DB.

-AAron

 

[a a r o n . k e m p f]

I'd guess an x64 version

I had a hell of a time using the x64 desktop.. I finally used the 32
bit Internet Explorer and it works now

-Aaron

 

[Ken]

Ok we use Adobe full for the pdfwriter version 4, it works fine on all the
pcs but when installed on the server 2003 , the pdfwriter v ersion didn't
load. Something called Distiller loaded.
So before I run out and buy something else, since the pdfwriter loads and
works perfectly on the pc's, what do I have to do to get it to load on server
2003, so we can utilize Terminal Services.
en

 

[Tony Toews [MVP]]

Ok we use Adobe full for the pdfwriter version 4, it works fine on all the
pcs but when installed on the server 2003 , the pdfwriter v ersion didn't
load. Something called Distiller loaded.
So before I run out and buy something else, since the pdfwriter loads and
works perfectly on the pc's, what do I have to do to get it to load on server
2003, so we can utilize Terminal Services.

We can't help you with an Acrobat issue. We can help you with Access
related issues which is why I suggested a non Adobe alternative.
Without an error message of some sort we can be of even less help. I
would suggest contacting Adobe.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/