Access 2002 on TS 2003

[Luke Bellamy]

Hi,
I have an Access 2002 runtime application that runs on a Terminal Server
2003 (small
business server). I have found that when I display and try to print any
reports
it give me the Microsoft Error Reporting Tool (i.e do you wish to send this
error
report to Microsoft). Note this happens 95% of the time.

Just wondering if anyone knows about any incompatibilities between Access
2002
and Terminal Server 2003 or any gotchas that I should look out for.

Thankyou

 

[M.L. Sco Scofield]

Take a look at http://www.granite.ab.ca/access/terminalserver.htm. Tony has
a lot of comments and links to a lot of other sites that might help.

Good luck.

--

Sco

M.L. "Sco" Scofield, MCSD, MCP, MSS, Access MVP, A+
Useful Metric Conversion #16 of 19: 2 monograms = 1 diagram
Miscellaneous Access and VB "stuff" at www.ScoBiz.com

 

[Tony Toews]

Just wondering if anyone knows about any incompatibilities between Access
2002 and Terminal Server 2003 or any gotchas that I should look out for.

Not that I know of. However can you print from Word fine? Is the
default printer set?

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

 

[Luke Bellamy]

Thanks Tony and Sco... I found my problem.

Access XP runtime was falling over when my app would display/print reports
(yes displaying or priting). I spent all last night working this out and I
found
out that after I left the server admin changed the compaitiblility of my
application
by setting "allow non-administrators access" (found by right clicking on the
icon
in the start menu and selecting compatibility). As soon as I took this off
everything
worked 100%. I am not exactly sure what that function ("allow
non-administrator
access") does but I can only assume that when you do actually specify a
different
compatibility mode (which I didn't) it uses the mode you set for all
non-admin users.
But I'm not sure why Access RT 2002 did not like it.

 

[Tony Toews]

Thanks Tony and Sco... I found my problem.

Thank you very much for reporting this problem. My page has been
updated with credit to you.
http://www.granite.ab.ca/access/terminalserver.htm
And I've reported this to MS.

Do you want your email address on there? Or even your name?

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

 

[Luke Bellamy]

Excellent, Thankyou Tony. Email and/or name is fine by me.

Just checked it out on your terminal server notes which I'm very familiar
with
From reading it I interpreted that by setting "allow non-administrators
access" fixed the problem where infact it was the reverse.
If this is the case I put a few extra comments in the paragrah to reflect
this.

"About 95% of the time whenever a report was previewed OR printed Access
displayed the Microsoft Error Reporting Tool "do you wish to send this error
report to Microsoft?". The server admin HAD SET THE compatibility of my
application by setting "allow non-administrators access" (found by right
clicking on the icon in the start menu and selecting compatibility). This
caused the problem and once this was unset reporting worked correctly."

 

[Tony Toews]

Excellent, Thankyou Tony. Email and/or name is fine by me.

Just checked it out on your terminal server notes which I'm very familiar
with

From reading it I interpreted that by setting "allow non-administrators
access" fixed the problem where infact it was the reverse.
If this is the case I put a few extra comments in the paragrah to reflect
this.

"About 95% of the time whenever a report was previewed OR printed Access
displayed the Microsoft Error Reporting Tool "do you wish to send this error
report to Microsoft?". The server admin HAD SET THE compatibility of my
application by setting "allow non-administrators access" (found by right
clicking on the icon in the start menu and selecting compatibility). This
caused the problem and once this was unset reporting worked correctly."

Gotcha. Updated.

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