Thanks for your response, but I would like to make clear that this COM object has no GUI and simply takes the frx that is named and saves the results out to disk as a PDF. Again, creating an instance of this same COM object from inside VFP works beautifully. Unfortunately, ASP.NET is trying to call this particular method and it executes right through the call to the print driver, but no output is generated. Another tidbit of note is that other methods from this same object execute successfully when called from ASP.NET.
Does this clarify the problem?
Thanks!
>You can't call an application from a VFP mtdll that has any kind of an GUI interface. The answer is to use a "file-based" VFP server where you need to do such things. WWC "file-based" is one way. ActiveVFP 2.0 will also have a "file-based" mode to make this possible and interact with the rest of the VFP mtdll seamlessly...
>>I have a need to be able to call FoxPro Reports from ASP.NET and display them as a PDF in a browser. In order to accomplish this, I am using Rick Strahl's wwPDF calling the Adobe Acrobat PDFWriter from inside a VFP 7 COM wrapper. This object accepts the report file name and other parameters and saves the resulting PDF out to a specified location. This works all well and good when I call it from Fox. However, when I create my reference in .NET and call the exact same method, it does not save the file out.
>>I have placed several debug STRTOFILE() statements in the COM object that let me know the code is executing in its entirety, but for some reason the file just isn't getting to the PDF printer driver.
>>I have guessed that this is somehow security related, but I have changed the machine.config to allow the worker process to run under the SYSTEM context. I also configured the COM object(in Component Services) to use both a specified local administrator as well as the launching user (SYSTEM) on separate tests to no avail. Also, there are no restricting NTFS permissions on the drive.
>>Does anyone have an idea what the issue might be? By the way, I am running on Windows XP Pro for now and plan to distribute to a Win2K server.
>>Many thanks for your feedback!