>>Thanks Boon Seng Wong
>>
>>Do you think the error can be caused even by reports that are part of the project but not printed at the moment of the crash ?
>
>** I don't think so.
>
>>
>>Example:
>>I print an Invoice and it works fine.
>>Then when I open the Purchase screen do create a new purchase, the application crashes before I even try to enter details or click the Print button.
>
>** This sould be cause by your programming error. Do you have any grid in your Purchase screen, and setting the wrong control source for the column?
>
>==> If I put the old dot-matrix printer back the application never crashes, so how could the problem be related to the grid ? That's why I thought the whole problem could only be related to reports/printers...
>
>>
>>So should I clear TAg, Tag2, EXPR(partially) fields for all reports ?
>>I thought that cleaning the ones involved in the operations that cause the crash would be enough to see if the solution works.
>>(I'll clean them all, of course, I'm just trying to understand if there's any logic in what I'm doing...usually there isn't...he he he)
>
>** Since I include the report file in my EXE, I need to clear the TAG & TAG2, EXPR so that the SET PRINTER command can work for others printer in my EXE, else the report will fixed to the printer during the report


Do you have any code inside the form, classes, function, procedure, etc... which contain any command related with the report/printer?