Rich

Another thing you might consider:

Check to see if the machine you are getting the error on has a printing system installed instead of using a Microsoft driver for the operating system. If so, un-install and use the proper driver from Microsoft.

We used to battle HP printing systems all of the time regarding this setup.
Recently, we found another setup of a printing system built for a Dell printer
(actually a lexmark printer in disguise)


A good way to see if it is a printer driver or also a video driver conflict is to run the report while in safe mode and see what happens.

It might lead to something...



>>>What could cause the Work Area to change in the report. There are no UDF's which could do this. There are some Data Groupings......could that be the cause????
>>
>>That might happen if the printer has tables in its DataEnvironment. As a standard precaution, I take out all tables out of the DataEnvironment, especially when a report starts to do queer things.
>
>Thanks for the reply.
>
>The report does not use a private data session. When I open the DataEnvironment in the report it is empty. I checked the FRX and found a record for DataEnvironment. This is what was in the EXPR field

>Top = 0
>Left = 0
>Width = 0
>Height = 0
>DataSource = .NULL.
>Name = "Dataenvironment"

>
>If you have any other thoughts I would appreciate hearing them.
>
>Thanks again..........Rich