Haven't seen this twist:

We always trash out the printer info in record 1 of the FRX's (from EXPR and TAG/TAG2), and all has been fine until now. Suddenly some of my users are experiencing runtime errors: 'Error Loading Printer Driver' when running REPORT PREVIEW, with Message(1) = '0'. The flagged line of code is in the FRX at a record containing a calculated field, and the TAG field in the FRX contains simply '0' (zero). These reports have several calculated fields, and every one has this TAG field value. The only literature I have seen says that TAG and TAG2 are for binary printer info before and after (init & de-init?), but always refers only to record 1, and these are in later records...

The question is: Is it safe to just clear ALL TAG and TAG2 fields, or is this an undocumented flag for calculated fields in the FRX?

This is a production-down problem -- but only randomly occurring (ie: I ran the same report with the same data files later and had no problems, but it has occurred again since...) -- so any help is urgently requested.

TIA.

Rob