>Well it was VB holding the reference, I guess it held it after trying to access it for the build even tho the build failed. So now I can try again. I may have to post more questions on actually creating these things tho. This is a pretty steep learning curve, at least for me.
>
>Thanks,

Bill,

The one thing that either I missed or you didn't say was that, according to your later posts, this is an OLE Automation DLL and not a standard C DLL. Is this correct? I've never had a problem with VC++ (or other language for that matter) compiling unless some reference was being held to either a function or the object that's been created. Simply setting the reference to NULL or CLEAR DLLS usually clears things up. There is an exception, however, that applies to automation servers. Habitually, I call the DllRegisterServer() function from VFP. If I need to re-compile during a session where I've called it, I need to CLEAR DLLS prior to the recompile.

And no, I wouldn't dream of "twit filtering" you.:-)