This is one I don't understand. I'm porting a heap of code out of an excel
class module into a VB6 activex dll for security reasons, and to provide a
multi-app interface that I can use in Word later.

It works fine, much to my surprise since I've always been horribly confused
about com add-ins and such, but every time I amend the code in the dll and
recompile it, when I reload the code in excel that has a reference to the
dll, I get a Misssing error even though the recompiled dll is in exactly the
same place as before.

The solution is fairly simple but very annoying: goto Tools, Reference,
uncheck the missing reference, click OK. Then do it again, Tools, Reference,
the reference is there without a missing flag this time, and I can reselect
it with no problems.

Any suggestions as to what is going on and how I can stop this? Would it be
a changing prog ID or something that is being done during the compile in VB?

Thanks,

Robin Hammond
www.enhanceddatasystems.com

I've done little with regard to DLL compatiblity, but I know there are
options for Project and Binary compatibility under the Project properties.

I believe this means that you can replace the DLL file without having to
re-register it.
It may or may not help you with this issue.

--
Rob van Gelder - http://www.vangelder.co.nz/excel


"Robin Hammond" wrote in message
...
This is one I don't understand. I'm porting a heap of code out of an excel
class module into a VB6 activex dll for security reasons, and to provide a
multi-app interface that I can use in Word later.

It works fine, much to my surprise since I've always been horribly
confused
about com add-ins and such, but every time I amend the code in the dll and
recompile it, when I reload the code in excel that has a reference to the
dll, I get a Misssing error even though the recompiled dll is in exactly
the
same place as before.

The solution is fairly simple but very annoying: goto Tools, Reference,
uncheck the missing reference, click OK. Then do it again, Tools,
Reference,
the reference is there without a missing flag this time, and I can
reselect
it with no problems.

Any suggestions as to what is going on and how I can stop this? Would it
be
a changing prog ID or something that is being done during the compile in
VB?

Thanks,

Robin Hammond
www.enhanceddatasystems.com

Thanks Rob. Project compatability seems to fix it.

Robin Hammond
www.enhanceddatasystems.com


"Rob van Gelder" wrote in message
...
I've done little with regard to DLL compatiblity, but I know there are
options for Project and Binary compatibility under the Project properties.

I believe this means that you can replace the DLL file without having to
re-register it.
It may or may not help you with this issue.

--
Rob van Gelder - http://www.vangelder.co.nz/excel


"Robin Hammond" wrote in message
...
This is one I don't understand. I'm porting a heap of code out of an
excel
class module into a VB6 activex dll for security reasons, and to provide
a
multi-app interface that I can use in Word later.

It works fine, much to my surprise since I've always been horribly
confused
about com add-ins and such, but every time I amend the code in the dll
and
recompile it, when I reload the code in excel that has a reference to
the
dll, I get a Misssing error even though the recompiled dll is in exactly
the
same place as before.

The solution is fairly simple but very annoying: goto Tools, Reference,
uncheck the missing reference, click OK. Then do it again, Tools,
Reference,
the reference is there without a missing flag this time, and I can
reselect
it with no problems.

Any suggestions as to what is going on and how I can stop this? Would it
be
a changing prog ID or something that is being done during the compile in
VB?

Thanks,

Robin Hammond
www.enhanceddatasystems.com