>>>I'm trying to automate report generation on a Web site and found that the dll I created with Fox 6 didn't like the Report Form line in my code. Which was a surprise to me because I thought pretty much all the commands (with some obvious exceptions) were available for use in COM creation. So my question is - is there a way around this? and is there a list somewhere of "prohibited" commands that can be used in EXEs but not DLLs?
>>
>>The VFP team really goofed, and did not include REPORT FORM support in the in-process servers (how the heck are we supposed to create PDF files?). Hopefully in the next version, or in an upcoming service pack...
>>
>>You can do what you want to do by creating an out-of proc exe server to handle your printing, and calling it from your in-proc dll.
>
>I tried creating an out-of-process server to handle the printing, and calling it from the in-process server, but the very same thing happened ("User interface operation not allowed at this time" on the REPORT FORM line). This time the error happened when the object was instantiated and run in Fox 6, and I didn't even get to the browser testing phase. Before, it ran fine in Fox.
>
>What happens to the cursor created in the DLL? Is it available to the EXE?
>
VFP cursors do not cross COM boundaries.