>>>>>If you don't know the ProgID, and don't know the name of the .DLL or .EXE used to implement the server, what piece of information will you have that will allow you to identify the server?
>>>>
>>>>Maybe I need to explain again what I want to do. I build a class in VFP and compile it as a DLL. On the build dialog I can set the version number for the DLL. In the class, I want to be able to get and return the version number of the DLL. This is easy with AGETFILEVERSION(). But, I have to know the full path and file name for the DLL, which I won't always know. So, from inside the class, how do I figure out what DLL it is in?
>>>
>>>Just a SWAG, but have you tried FULLPATH(SYS(16)) in the Init method of the class?
>>
>>I get the VCX information from that, not the DLL.
>
>That doesn't make any sense, since the .VCX won't be there while the .DLL is executing. How can it resolve the .VCX path on a system with no .VCX? or does it resolve to the compile-time location of the .VCX, which would be even more confusing
I never actually tried FULLPATH, but SYS(16) alone returns information on the class library. There is nothing about the DLL included. I don't see how FULLPATH can make a difference here.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer