>>A client just upgraded to VFP 5.0 from Fox for Windows. He can run the same report, same code, and it prints much slower in VFP than it does in FoxWin.
>>
>
>Hmmmm....that takes just some simple experimentation to see what can be optimized.

In theory, yes! We've tried creating the same report in VFP that we have in FoxWin, and it still runs much slower and most the time, can't find the correct printer. Their NT consultant has checked out the server, says it's fine, yet the server seems quite slow to me.

I've heard that FoxWin handles printer calls basically through DOS whereas as VFP uses Windows. I'm suspecting some weird sequence of errors of VFP interfacing with the Win95 print drivers and NT, but am not sure what.

Any ideas of what to optimize appreciated!


>>Also, VFP seems to have much more trouble finding the correct printer than does FoxWin. SET PRINTER TO \\ works fine in FoxWin but doesn't in VFP.
>
>SET PRINTER TO NAME WindowsPrinterName....that's the right command.

That's the syntax I meant, and the syntax we use, still doesn't find the printer.