I just tried this in vfp8 and got a different message when trying to run as a .dll. Mine is "User Interface operation not allowed at this time" which would indicate that somewhere in the source it's using a UI element which is not allowed in a mtdll. This may be the same reason you're getting the error. You could either search the code for this or try their debugging mechanism, odebug.prg(I could never get it to work). This would be a nice time for the MS people who wrote or support this stuff to chime in here and explain it.
FWIW, I gave up on foxisapi and the included examples a long time ago because they were buggy and not supported. It's far easier to create a .vfp. mtdll with your fox code and call it from ASP.NET or ASP. The performance is as good or better than foxisapi and you can also debug. Check out some examples and free tool at: http://www.activevfp.com/avfpdemo2/default.aspx .
>Hi,
>I have just started to learn how to use VFP in a web application. For this reason I have studied the sample that come along with the VFP8 program. In the help documentation “FoxIs, a Visual FoxPro Internet Server” you can follow the steps how to do. When you come to “Running as Automation server” you can read “Once the FoxIs sample has been compiled into a .exe or a .dll…..” and “You can create an object…” by the following code in the command window:
>ox = CREATEOBJECT('foxis.employee')
>ox.SHOW
>This works with the .exe file but with the .dll file I receive the following error message:
>“OLE error code 0x80040111: ClassFactory cannot supply requested class”
>When I use the sample together with IIS and the FOXISAPI I receive the following result with the compiled FoxIs.dll in the Inetpub\script directory:
>“FOXISAPI call failed
>Progid is foxis.employee
>Method is startup
>CoCreateInstance failed with err code 80004005: Unspecified error “
>With the compiled FoxIs.exe it does work and generate html-pages wonderful. What do I do wrong when I try to use the automation server as a .dll file?