Hi,

I have a spreadsheet that uses a COM dll in the VB code. For testign
purposes I have had to use a new version of the dll and lace it in a
different directory to the original and then regsvr32.

I find that the excel code seems "confused" as to the symbols of the
COM dll now referenced correctly to the new directory. In order to
unconfuse VB i must dereferene the project compile then re add the
reference and recompile. This sorts out my problems.

My issue is that I have multiple users using different versions of the
dll, how can I avoid or fix this annyoign issue?

In VB, the trick is to set your project compatability to binary.

Robin Hammond
www.enhanceddatasystems.com

wrote in message
oups.com...
Hi,

I have a spreadsheet that uses a COM dll in the VB code. For testign
purposes I have had to use a new version of the dll and lace it in a
different directory to the original and then regsvr32.

I find that the excel code seems "confused" as to the symbols of the
COM dll now referenced correctly to the new directory. In order to
unconfuse VB i must dereferene the project compile then re add the
reference and recompile. This sorts out my problems.

My issue is that I have multiple users using different versions of the
dll, how can I avoid or fix this annyoign issue?