Well, the rationale for using GetObject is probably so you can reuse the object handle to the server instead of creating a new one. I know this works when using automation with something like Excel. I guess you would need to test to see if it's working with your COM+/vfp mtdll. Test createobject and see if it's actually creating several processes and then test getobject. You could see this in the Task Manager processes although this is a dll, so, I'm not sure this will work. My hunch is it doesn't matter one way or another since this is a dll ...
>Can someone explain the difference between using GetObject and createobject to access my VFP COM dlls from web pages and other dlls?
>
>I have a consultant recommending that we change all the createobject to getobjects to force only one object to be created. All the dlls in question will be in MTS/COM+ (Win2k) packages.
>
>Why would I want to do that? Why not?