O
Oscar
I've programmed a Visual Basic dll which is referred to within the Excel VB
after that I've set a reference to this dll within the Excel VBA add
reference dialog. Anything works good until the moment when I compile a new
version of the dll and replace the old one (just by copying). Each time I do
that, Excel reports
error 430 , class doesn't support automation or expected interface.
The only way to have the new dll running, is by removing the existing
reference to the dll first, close the add reference dialog, open the add
reference dialog again and setting the reference to the dll again. Is there
a way to overcome this, or automate these last mentioned activities by
coding ?
regards,
Oscar
after that I've set a reference to this dll within the Excel VBA add
reference dialog. Anything works good until the moment when I compile a new
version of the dll and replace the old one (just by copying). Each time I do
that, Excel reports
error 430 , class doesn't support automation or expected interface.
The only way to have the new dll running, is by removing the existing
reference to the dll first, close the add reference dialog, open the add
reference dialog again and setting the reference to the dll again. Is there
a way to overcome this, or automate these last mentioned activities by
coding ?
regards,
Oscar