Zlatin,

Have you asked this question on the ww message board (http://www.west-wind.com/wwthreads)?

>Yes, I have seen the dialog - see my first post.
>
>Actually, it is out-of process COM server and I have read the article (I have the book "Internet Applications with Visual FoxPro 6.0" and the article is contained in that book). The problem is that, when invoced from an ASP page or through FoxISAPI, the COM does not do anything, but raises an error. It does not raise an error when I invoce it in FoxPro development environment. I have tryed also to instantiate VisualFoxPro.Application and to script the report printing to file (this with external FRX) but, it does not print.
>Regards
>
>>Zlatin,
>>
>>The report writer uses a dialog message ("Printing...") that causes this error when called from an in-process COM DLL. Can you build your COM into an out-of process EXE?
>>
>>The following article describes the problem: http://www.west-wind.com/presentations/pdfwriter/pdfwriter.htm
>>
>>HTH