>>>I have a Foxpro for DOS 2.6 application. Each of three pcs prints differently. They all have Windows 95 and point to the same exe on a Netware 3.12 server and print to the same networked printer.
>>>
>>>PC #1: prints immediately
>>>PC #2: prints after the dos application exits
>>>PC #3: prints after logging out of Netware
>>>
>>>Has anyone seen this type of behaviour? Any ideas?
>>
>>Check the users' Novell login scripts re how the CAPTURE statements are set up. It may be that the timeout setting is different from one user to the next. Also, in your code, doing a SET PRINTER TO immediately after the REPORT FORM statement will flush the printer buffer.
>
>Each user has the same login script (the system login script). I don't have access to the foxpro source. Any other thoughts?

If the same app is behaving differently on different PC's, it's not the app. So, it's a configuration issue of some kind. I think Ed's comments are on target, have you explored each workstation's Win95 printer settings? Under the Detail tab, you have Timeout settings, Spool settings, and Port settings; you might want to check and see if they are the same on all three PC's.

On PC's #2 and #3, how long are you waiting before deciding it's not going to print? I've seen situations (on more than one kind of network, by the way) where it sometimes took several minutes for something to start printing, but if you waited long enough it eventually printed. Try this: send a print job from PC #2, don't exit the app, then send a print job from PC #1. Does #1 print immediately? Does #2's job come out ahead of it? Or do both get "stuck" until you exit the app on PC #2?

In my experience, the answer in these cases usually turns out to be a timeout setting buried somewhere in the labyrinth of user and/or workstation options. They're often a bear to find, though.

HTH,
Rick