There is nothing inherently wrong with putting kixforms.dll (any COM object actually) in a seperately directory. In fact, I have mine sitting in a directory called C:\kixforms\release, but Les's point about putting it in SYSTEM32 has validity, but just not necessarily in your case.

Since you are providing the full qualified path to the DLL, it should work and in fact does wortk. The "gotcha" with doing this lies with REGSVR32 itself - its has some (imho) strange behavior. If one doesn't specify the fully qualified path to regsvr, it FIRST looks in SYSTEM32 for the DLL and if found, registers that one, only if its not found in system32 will it look in the current directory. Its kinda ass-backwards in my mind.

I have been bitten by this many times in the past since i tend to register the DLL by hand, and i dont usually specify the full path. If i have an old copy in SYSTEM32 it takes that one instead. Then i proceed to bang my head against the desk wondering why my changes arent taking effect.

Anyway, these comments are NOT directed at you because from what I can see, you are doing all the right things. I think what we will need to see is the piece of code that checks for registration and that pumps out this message.

-Shawn

[ 10. June 2003, 14:51: Message edited by: Shawn ]