So, it should work as a COM EXE? My app is compiled as a COM EXE and the REPORT FORM is causing the app to freeze. Just to test, I compiled it as a COM MTDLL and I received a "FEATURE NOT AVAILABLE" error. I wish some sort of error would occur in my COM EXE to see what's going on. I'll keep searching for a solution. Thanks for your help.

>Hmm, the problem is usually that REPORT FORM doesn't work in a VFP COM DLL. >The solution to this is to put it in a COM EXE and call that from the COM >DLL! I suppose it may be a security issue in which case you would need to >go into DCOMCFG and set those properties to allow it to print. If there are >really no Interface elements at all, you might want to consider making them >into VFP COM MTDLLS since the performance can be twice as good...

>>I'm in the process of making 3 apps that are currently regular EXEs into >>COM EXE that will have no GUI - they will be installed on a server and >>accessed via a workstation using DCOM. 2 are working fine, but the 3rd >>seems to be having problems with REPORT FORM. I tried SET TALK OFF and the >>NODIALOG option for REPORT FORM to eliminate any GUI elements but it is >>still having problems. I've tried trapping the error but it seems to just >>freeze at the REPORT FORM command. I need to send the report to a printer >>but I've also tried TO FILE with the same result.
>>
>>Any help would be appreciated. Thanks.
>>
>>Aaron