P
PM
Hi!
My VBA program calls a custom dll. It works fine.
I now move to another computer and install the dll. When I launch my Excel
program, it cannot find the dll.
I can fix this manually. I open Tools>References eliminate the reference
(which is "missing"), close the box, then open it again and tick the
reference to the dll which is indeed present in the list. That procedure
works fine.
How can I program this in order not to perform this simple but very
inelegant manual procedure (and not feel stupid explaining this to
colleagues!)?
If I try to use AddFromGuid, I need the guid. But when I check for the guid
with Excel ("for each ref in vbprojet.references etc."), I get the guid of
the dll on the first computer. So, in my feeble understanding, I need to
search the correct reference to the dll on the actual computer I am working
on. I don't know how o do this. Perhaps use a Windows API? Or is there a
simpler way within Excel?
Thanks for any tips!
Pat
My VBA program calls a custom dll. It works fine.
I now move to another computer and install the dll. When I launch my Excel
program, it cannot find the dll.
I can fix this manually. I open Tools>References eliminate the reference
(which is "missing"), close the box, then open it again and tick the
reference to the dll which is indeed present in the list. That procedure
works fine.
How can I program this in order not to perform this simple but very
inelegant manual procedure (and not feel stupid explaining this to
colleagues!)?
If I try to use AddFromGuid, I need the guid. But when I check for the guid
with Excel ("for each ref in vbprojet.references etc."), I get the guid of
the dll on the first computer. So, in my feeble understanding, I need to
search the correct reference to the dll on the actual computer I am working
on. I don't know how o do this. Perhaps use a Windows API? Or is there a
simpler way within Excel?
Thanks for any tips!
Pat