Virusim,

When I said "I would take a look at the code" I meant to imply that you should, not literally that I was going to debug it if I had the code.

Anyways, I took a quick look at your Error() proc and I think you should put code to write the contents of the nError, cMethod, nLine parameters and the Message() function return value and possibly even a DISPLAY MEMORY to a file for aiding in the troubleshooting. If the rawprint class you are using returns error messages or has properties that get populated in the event of errors, try to access their contents too. HTH

>Hi,
>
>I will sent my code for you to had a look, hopefully you can
>help to find the bugs. Thank in advance.
>
>>I would take a look at the class method code if it's available. Or, try calling the Open() method in the command window without setting a printer, to see if that causes a printer dialog to come up.
>>
>>When you are logging the error, also write the values of all relevant properties of the object, like cPrinterName. If it works as an EXE, I would suspect that something is generating a dialog of some sort. After setting Sys(2335,0) the error produced would be "user interface operation not allowed at this time".
>>