Hi Harry,
See message#1057868 , it might help you resolve your problem
Rgds++
Sergio


>Yeah, I see the point (it aint a fix). What I found was that I could speed things up (by a factor of 10 by including the reportoutput and reportpreview apps in my own app. I could then dispense with the reportbehaviour 80 command.
>
>However, that's created - or revealed - a new problem altogether. A couple of my users updated their app to my new version and suddenly reported they couldn't print. It went through all the motions and appeared to print but nothing came out of their local printers. Why not? Because it was coming out of my local printer. Why? Because it was remembering the printer on which I'd designed the report and saved the Printer environment.
>
>No problem, I thought, just edit the report and tell it not to save the printer environment. No effect. Hmmm. Perhaps it needs to be told to use a different printer to "flush" the old environment (clutching at straws here). No effect. I even wrote a new line into the report printing routine to SET PRINTER TO DEFAULT so that every user would print to whatever their default windows printer was set to. No effect. Its all still coming out on my local printer! I even tried getting the report to screen preview, then before clicking the printer icon, using zonealarm to isolate the machine from the network so that it couldn't send the damn thing across the network to my local printer. It just hung and refused to go anywhere.
>
>This now qualifies as a major PIA!! Not only have I got to figure out how to get this damn report printing to the users' choice of printer, but I've got about a thousand other reports to worry about!
>
>If it wasn't for the fact that want $695 for that print engine you mentioned, I would have gone straight for that! But at that price I'll need some convincing.
>
>Help!!
>
>
>>This is no "fix", just a way to see where the problem really comes from. By setting reportbehavior 80, you give up most of the best features of VFP9! It's like driving downhill, your car goes much faster than normal, but sooner or later you have to drive uphill again. :-)
>>
>>By the way, I don't use the report engine in VFP9 at all, I use Rich Simpson's Mind's Eye Report Engine Control, http://www.mindseyeinc.com/ReportEngine/index.htm. It's much faster, and has a ton of extra features.
>>
>>>Nice one. So nice when there's a simple fix. Godnose how we were supposed to figure that out for ourselves. How did you come across that little "feature"?
>>>
>>>>New report engine takes more time for rendering pages, Try with
>>>>SET REPORTBEHAVIOUR 80 to see if the speed is changed.
>>>>
>>>>
>>>>
>>>>>even with trivial datasets on a standalone machine.
>>>>>
>>>>>Even from the command line, if I run
>>>>>
>>>>>REPORT FORM XXX PREVIEW IN SCREEN
>>>>>
>>>>>for a trivial report with a few hundred records
>>>>>
>>>>>it can take up to a minute to display the result.
>>>>>
>>>>>If I immediately repeat the command, it will typically halve the time.
>>>>>
>>>>>After four or five attempts, it is instantaneous.
>>>>>
>>>>>So it is clearly behaving like there is some kind of cacheing issue but on such trivial reports and trivial amounts of local data, this doesn't make sense.
>>>>>
>>>>>It's only been an issue since VFP9 and it seems to be more of a problem for me than my clients (fortunately - or they'd be ripping me apart!) Which suggests its something to do with the VFP environment but I can't track it down.
>>>>>
>>>>>Any suggestions?