Hi Evan,

By default VFP COM starts where the VFP runtime is. You can determine the folder with _VFP.ServerName property.


>Hi gang,
>
>I *know* I've seen an answer to this somewhere here, but I'm not having a lot of luck in finding it, and I'm hoping someone knows or the UT link gods can help me here (bg)...
>
>I've built a VFP EXE that I'm instantiating as a COM object from another VFP application. That EXE, when it initializes, needs to be able to find a specific folder on a specific drive. I have control over the folder name, via a contained property of the COM object; what I can't control is the ** drive letter ** where that folder exists for each installation of the calling application.
>
>I've thought about using an XML file for configuration, I've thought about using a config file, and I've thought about a table. Each one of them has the same issue -- how do you tell the COM object where the fool thing exists at runtime? Soooo....
>
>QUESTION:
>How does one find out, after it's been registered, the location where that VFP COM executable actually starts from? BTW, the app that starts this COM object will most likely be on another drive/path, but ABSOLUTELY will be on the same physical box (for now -- I'll deal with remote instantiation in the next version).
>
>TIA,