>Rick,
>>>I am experiencing problems running the FOXISAPI.DLL supplied w/ VFP5. I have compiled my Server EXE whith the Multi option, but the system seems to not be releasing the other copies of my EXE each time. The Instance count keeps rising in my LOG file. When I issue a 'Reset' CMD, the log file shows it recursively releasing all the instances since my last reset.
>>>

>>
>>How do you have your INI file set up in term of the number of instances
>>to run?
>>
>>> Could this be related to my problem getting the EXE to run as IUSER_MachineName?
Hi Ricardo,

>
>I'm not using your product yet;) I only had a few days to come up with a proof of concept demonstration for a client and didn't feel that I had the time to go through the learning curve of your tool, although if the project goes through, that is the way I will probably go.

This has nothing to do with Web Connection :-}... This is FoxISAPI's
pool manager I'm talking about.
>
>The problem I am experiencing is with the VFP5 OLE Automation Server example. Their docs tell me that I am supposed to set the flag to Multi use. I really do want to use multiple instances of the same server in my case so I don't have to go through the overhead of re-loading everything for each form request.

I know, but that's bad advice. Multiuse servers buy you nothing except they
prevent you from using the FoxISAPI pool manager to get mulitple simultaneous
requests processing.

For proof of concept that's not really relevant anyway though. A single
instance should work just fine.

>My understanding of the FOXISAPI dll is that is is supposed to release every instance that you don't clear the Dispatch pointer to 0.

FoxISAPI loads and releases each instance *unless* you set the
lnReleaseFlag parameter to 0 - again this is a silly default, since typically
you'll want to not unload the server unless you're debugging and you can
use the RESET method to release all instances.

What exactly is the problem you're seeing though??? Is the server
not instantiating or what?