Hi,
It is not bad advice, it will get the client back to performance levels they expect, giving him time to find what the actual problem is.

>Bad advice in this case. SET REPORTBEHAVIOR 80 is more relevant! However, you lose most of the new features. Nothing is free in this world, you know!
>
>>Hi,
>>For a quick fix (till you can find out what is causing the problem)try SET ENGINEBEHAVIOUR = 70.
>>
>>>After the debacle we all experienced years ago with the HP problem in VFP 3.0, I have a hard time believe the Microsoft would once again punish us on reporting performance. Yeah, the new features are cool to use but it is kind of like driving around in a brand spankin' new Porsche that maxes out at 30 miles per hour (48.28 km/hr!). So, what is going on with this and who signed me up for this torture?
>>>
>>>I have a report that in VFP 7 PREVIEWS (not even send it to the printer) in less than 2 seconds. The same report in 90 previews in a "smoke a cigarette" 262 (4 minutes, 22 seconds). Even running in 80 takes a long time. No pictures, no graphics, just text. There are some formulas that call VFP programs to retrieve data, etc. but it isn't anything major.
>>>
>>>In addition, if the user actually wants to PRINT, under 80 or 90 it sends a page, waits until the printer prints a page, sends another page, waits, etc. Crazy. Yes...the printer setting is set to spool so don't think i'm trippin out. The only thing that is "unique" is it is a local printer (wow) being sent over a LPT cable. Even printing over a network takes awhile. For those of you interested, the file size under 90 is 3.37 MB and under 7.0 it is 268kb.
>>>
>>>My users are royally ticked because they don't understand the "well you should see what this thing really CAN do". Don't get me wrong, I love VFP but this is absolutely crazy. Are there any solutions, tips, payoffs to this debacle or did i miss something in the help file?
>>>
>>>Thanks for the help and have a good day-
>>>
>>>Geoff