>I would appreciate any opinions about running a FoxPro 3.0 executable unders Windows 3.1 (Novell network). We had a vendor develop a system for us under FoxPro 3.0 in their Windows 95, 32 bit ennvironment. When they run the executables on our Windows 3.1 & Novell environment some things don't work. Specifically, they cannot get print functions from the FoxPro app to route to the appropriate network printers. Even coding to route direct to the LPT ports doesn't work (LPT ports are assigned to network printers).
> The vendors position is that WIN32S should allow the 32 bit executable to run under Windows 3.1 but it's not working.
>
> Thanks for any input.
>
>Dave
Your problem may be similar to the one I encountered developing in NT and the users using 3.1. I was sending data to a bar code printer on a network print queue using the SET PRINTER TO \\machinename\queuename syntax. This worked great in NT bu would not work in 3.1. I discovered that you have to use SET PRINTER TO NAME windowsprinter name for 3.1. The printer has to be set up in the Control Panel for the printer type. I believe the network people did the CAPTURE command from DOS before starting Windows and connected the printer to the LPT port specified in the CAPTURE. Use ? GETPRINTER from the command window to determine the printer name to use for VFP. The name that shows in the control panel is not the name VFP wants. In our case the control panel showed something like Generic / Text Only on LPT2 (quename). The printer name VFP wanted was just Generic / Text Only