Subreports in Terminal Services

[BACinTX]

I have some reports in an 2003 database that are made up of subreports.
These reports work great on my hard drive and when accessing them on the
network server through my Windows Explorer; but, when accessing them on the
network through Windows Terminal Services (which is what we are using to have
our front end users utilize the database), these reports never run and keep
saying Formatting Page, ctrl break to stop. Any ideas how to fix?

 

[Arvin Meyer [MVP]]

Do you have a printer set up in Terminal Services?

 

[BACinTX]

Yes...the session one network printer defaults are being used in Terminal
Services. There are several single reports (based on single entry in a form
field) that are working....these reports are made up of multiple subreports.
The ones that are not processing are what I will call bundle
reports....several of the single reports above that are grouped as subreports
in the bundle report master. They do work perfect on my hard drive and on
the network when not using Terminal Services. Thoughts?

 

[Arvin Meyer [MVP]]

I would copy one of the non-working reports, then delete all but 1
subreport. If it runs, add another, etc. until you find the one that's
causing the problem.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com