>>I've found very weird behaviour of REPORT FORM to FILE command. VFP app runs long nightly batch and sometimes launches REPORT FORM to FILE command to create some files to be used later on. Usually, it works OK, but sometimes "Printer not Ready" error generated. I tested the case and found that REPORT FORM to FILE still needs some printer to be connected with PC and if PC loses connection to Net Printer the problem arises. Is it right behaviour? I cleaned up 'Report Definition' fields from FRX file but still get the same result: if I remove printer from Win Print Setting (no default printer) REPORT FORM to FILE generates nothing! Any ideas? TIA.
>
>VFP "needs to know" the intended destination printer - even a disk file "printer" per se - is available in a way that is essentially independent of data in a report form definition file beyond initially identifying the intended "printer" - it's an inherent function of the "windows" and O/S process, not of the "Report Form" process.
>VFP itself is the "prime mover" in initiating access to the "destination" for any type of "print" output. First, from the frx file, VFP "learns" of the intended destination and then "looks" for it because the current printer driver - necessary for correctly formatting output - is used when the report is sent even to a text file ( unless "ASCII" is included in the report form print command line to generate a generic text file free of all "printer codes"). Then any related .frx file data comes into play only subsequent to the "output path" becoming "available" when it (the frx) then defines the nature of the output data stream to that path in order to then "format" stuff.
>So even though it is going to a disk file - like a double check, VFP (and windows) needs to "find" an available "printer" per se in order to complete the process and if there is not even a "default" printer, then there is likewise "technically" not even any "default" current printer driver available - hence windows says "Printer Not Ready" etc.. (g).
>
>You may be interested in checking out my comments under "RE: Selecting Pages to Print in VFP" which I think may explain this behaviour also. :)
>
>HTH. /psb.

Thank for your reply. Basically, I understand this behaviour. The problem is that sometimes PC cannot find network printer (network is really not reliable) and generates the error during night batch. Is there any way to 'disable' printer double-check (except installing special dummy local printer). ASCII clause is not an option, because will be COPY TO LPT1 later on.