>I have written a single threaded VFP .dll for use in a VB application. The .DLL works just fine, but I have run into a strange behaviour that has me stumped. If I make a change to the source code, recompile, reregister, pull it up in VB and reset the refernece, I get THE OLD CODE!?! I have chnged and added properties and procedures, but the old properties are there with none of the changes.
>
>I have found that if I use regsvr32 to unregister the .dll, I can still find references to it in the registry.
>
>If I totally cahnge my project name and the output file created, it works just fine. If I change it back, I get the old references again.
>
>Any help or explanation would be appreciated.
>
>Thanks.

Edward,

I don't know if this will work because I haven't tested it. I personally don't use RegSvr32 to register and unregister the servers. Each VFP DLL has self-registering functions built in that can be called to perform the register/unregister tasks. Here are the declarations

DECLARE INTEGER DllRegisterServer IN < dll filename >

DECLARE INTEGER DllUnregisterServer IN < dll filename >

The < dll filename > represents the fully qualified file name of the DLL. Personally I've wrapped these functions in prgs. They call GETFILE() to retrieve the file name, declare the function in it, make the necessary call, and return the value of the dll call. This saves a lot of time doing the register/unregister process.

As I said, I don't know if this will help, but you might want to give it a shot.