>>>>We have a customer who has been using our program successfully for some time. Recently, however, he has been unable to print reports to the network printer. He gets the message, "Program Error: Printer Not Ready." No printer dialog box appears. Print preview works OK. He claims the only thing that has changed about the system is that he installed some new accounting software on his machine. What could be the problem?
>>>>
>>>>Our application is written in FPW2.6a. The reports are printed with statements like "REPORT FORM SERVCODE NOCONSOLE TO PRINT". The customers computer is on a Novell Netware network. The printer is attached to the server; it is an Epson inkjet. Other programs on his machine can print fine.
>>>>
>>>>What could cause the error message? What can we do to clear up the problem?
>>
>>>Did you clean up FRX file from printer-specific info (expr,tag,tag2 fields)?
>>
>>This is an old message, which I would like some clarification. When should you clean up the expr, tag, tag2 fields? Does left over printer info sometimes cause a problem, or always cause a problem? When you say "clean up", do you mean empty?
>>
>>Thanks - Brenda
>
>Clean-up means empty Tag,Tag2 and printer-specific part of Expr. The leftover info may cause a problem if it will happen to be identical with some printer setting on client workstation.

I've also faced this problem - and it's a royal PITA! You do need to clean up (empty) the tag,tag2 fields in the frx. I'd also pack it. My reports are all excluded from the projects. I tried including them and that didn't work either. So I also marked the report files read only. This worked from some of them, but not all. What I ended up having to do was to programmatically copy the report files to the work station hard disk and run them from there. I HATED doing it, but it was the only way I could get a couple of them to work. (And yes, I tried recreating the forms from scratch, but they still just wouldn't run.) At the time, I suspected that the root cause of the problem was printer drivers but I just never could figure it out... I don't necessarily recommend you do what I did, but you might want to test it and see if it helps you solve the problem.