EricDraven
Programmer
Hi all,
In my application there are numerous reports all created with QuickReport. These are all stored in DLL's to keep the size of my application down and they all work fine. One of my users however, called a report which previewed on screen correctly. When he came to print the report however (using the standard QRPreviews print button) he received an error code 87, incorrect parameter. I am assuming this is due to a conflict with his printer as the reports print fine on everybody elses systems. The problem is that the reports use Queries and Bands which mean that my tables (Paradox) have to be open to print. Receiving this error caused the DLL to crash which in turn locked the tables meaning the application couldnt work correctly either.
Seeing as I dont know what code is behind QReports print button, I was hoping that there is some nifty way of using the application to check whether the DLL has crashed and release it correctly?
As you can probably tell, I am rapidly running out of ideas here!
Cheers in advance
When your feeling down and your resistance is low, light another cigarette and let yourself go![[rockband]](/data/assets/smilies/rockband.gif "[rockband] [rockband]")
In my application there are numerous reports all created with QuickReport. These are all stored in DLL's to keep the size of my application down and they all work fine. One of my users however, called a report which previewed on screen correctly. When he came to print the report however (using the standard QRPreviews print button) he received an error code 87, incorrect parameter. I am assuming this is due to a conflict with his printer as the reports print fine on everybody elses systems. The problem is that the reports use Queries and Bands which mean that my tables (Paradox) have to be open to print. Receiving this error caused the DLL to crash which in turn locked the tables meaning the application couldnt work correctly either.
Seeing as I dont know what code is behind QReports print button, I was hoping that there is some nifty way of using the application to check whether the DLL has crashed and release it correctly?
As you can probably tell, I am rapidly running out of ideas here!
Cheers in advance
When your feeling down and your resistance is low, light another cigarette and let yourself go
