> Hello!
>
> This is more an operating system/networking problem than a Foxpro problem per se, but I wanted to see if anyone else has had any similar experiences with this. Here's the situation:
>
> We are gradually upgrading our company's workstations to Windows XP so that we may move from FoxProDos to Visfox 8. Our orders printing program had capture commands in them to direct the output to the printers, but since Windows XP doesn't like capture commands I replaced those with "SET PRINTER TO LPT#" commands, with the printer ports being managed by the login scripts. Now, get this: on the Windows XP station that I use the program works great and the print job goes directly to the LPT and prints fine. However, in the Windows 98 stations the same program returns either a "Printer Not Ready" error, or, if the job happens to make it to the LPT#, it just hangs there, indefinitely stuck in "Adding" status and never prints UNTIL I shut down Foxpro, at which time it begins printing!
>
> Any experience, ideas, thoughts, suggestions, recipes, fixes, for this?
>
> Thanks,
>
> Brian T in Cincinnati
>

I had the same problem (and more) when upgrading a system that is using Novell 4.11 and Windows 98 workstation.

My final solution was:
1. Don't use Windows XP.
2. Create a batch file for Windows 2000 station that do the printer redirection using the "NET USE" command
3. Create a batch file for Windows 9x stations that do the printer redirection using the "CAPTURE" command, this was done since the "NET USE" command is not available in Windows 98.


Hope this helps.

Regards, have a great day and a better tomorrow!
Bob Schroen - Canada