>>I have created an OLE application server using VFP 5.0, and have set the instancing to multi-use. I am accessing this object through ASP, using the Server.CreateObject command, and everything works great for the first instance of the object, but the server cannot create a second instance. If I build the OLE server with instancing set to single use, I can get as many machines as I want using it, but each one causes an instance of the object to load into memory. Does anyone know how to get multiple instances of the same object running, without loading the VFP runtime file into memory each time?
>
>That's the way it's supposed to work. Multi-Use servers are a single instance receiving multiple client requests.
>Visual FoxPro is a single threaded application so it cannot process more than one request at once *unless*
>you run multiple instances. InProc servers are always multi-use and cannot be configured otherwise.
>
>It doesn't matter with Active Server Pages though. No matter how you slice it, VFP will not process requests
>simultaneously either with inProc or OutofProc servers in ASP due to some limitations in the ASP
>implementation (actually if your VFP server goes UI idle you can but that doesn't count ).
>
>VFP 6 will feature apartment model threading which will allow multiple instance of the runtime
>to fire up automatically with DLL InProc servers. This is not possible at this time, but even then
>you're stuck with a new runtime for each simultaneous instance.
>
>For VFP 6 the key will be to run in Transaction Server which can manage multiple instances of
>VFP without special coding. Same rules apply except you don't have to worry about the management
>aspects.
>
>Since all of this is what MS says we'll have to say how well it'll all work when the time
>comes. I know MTS 2.0 is not all that it's cracked up to be at this stage of the public
>beta (IIS 4.0 and MTS 2.0 Beta 3 are available on the MS IIS site).
>
>Regards,
>
>+++ Rick ---

Thanks RIck. That was the answer I was looking for. I did manage to get it to load only one copy of the executable by using it as an application object, but multiple instances would be much niceer.

Rick