>Hey! I just posted a message on this today, but missed your earlier thread...
[snip]
>For administrative reasons, I cannot easily experiment with the possible solution on my end at this time, but maybe this will help you to solve it, and if so, please post the results.

>Thanx.
>
>Rob

Okay, I finally got it to print! But it turns out my problem *was* an NT problem and not VFP. I had to make everyone a print operator and do some extra registry work to get things going... It also made a difference how I added the printer to windows. WinNT shows the shared printers available on the network but you can also expand the view of a computer on the network and select a shared printer from that specific computer - It turns out this way isn't so good. I had the "spoolss" process taking up more and more memory after I tried to pop up the properties dialog for the network printer. If I selected the shared printer from the main list (shown above the computers) then everything was fine. This happened only on one computer so I don't know if it's the setup or some NT wierdness.