Will try, thanks
Mark


>Hi!
>
>Second EXE can generate the error and stay in dialog (modal) state stopping the entire process and waiting for input from user (but there could not be input because EXE is hidden).
>
>Take a look to the sys(2335) (Unattended Server Mode). You can use it to disable any modal state in your EXE with COM objects. Use it in the Init event in the COM object in second EXE file.
>
>BTW, when you use COM objects from DLL module, they run in unattended mode automatically.
>
>This way, at least, you will catch a code line that cause modal state or even error (situations like Open dialog box for table in case certain command have no current alias or cannot find certain table).
>
>HTH.
>
>>I have ASP based Web. An asp page calls fox EXE for data proccesing. This EXE CREATEOBJECTs from another EXE which actually does all the job and prints reports using PDF converter. Sometimes second executable is not released by the Web server and Web stops to serve clients. Request from Browser takes very long time (progress bar moves very slowly to the right). If I kill second process manually via Task Manager everything is OK again. This problem happens not too often. Sometimes it takes a day, sometimes a week. Please any idea?
>>
>>Thanks Mark