Resistry loses VB6 DLL

I have an Active-X DLL compiled in VB6. I registered it with Regsvr32.exe. A VB6 EXE calls the DLL. Every now and then I have to re-register the DLL to get the EXE to work. Why?
LVL 1
Neal HartmanAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

bhamiltoCommented:
Are you recompiling the DLL?  If so you need to set it for binary compatibility.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gcs001Commented:
Also remember that binary compatibility will not save you from having to re-register the control in all instances.
If you add more functionality in the DLL that changes the workig of the DLL you would have to re-registr it.
But it is a good idea to set it to Binary compatibilty as bhamilto said.
JetScootrCommented:
A couple of pieces of info are needed to answer, but I'll try to answer in each situation.  First: Is the DLL reg dat 'disappearing' from the machine that is being used to compile it? If so, as said before, check binary compatibilty.  If not, for example, if you're compiling it, running "package and deployment", and installing on a client PC, check these:
1> Is client PC on a network with NT as authenticating server?  I've seen cases where registry entries, downloaded by NT login script, overwrote (or overrode) locally installed registry setting.  Have not seen this on a Novell network, or on NT networks where system login script isn't being run at login time.
2> Were you logged in as W95/98 user or as "admin" when installing?  best bet:  click "Cancel" on the windows login screen, that is, startup without logging in prior to doing any install.  I've seen cases where this did make a difference - particularly the VB 6.0 Addins!  If you're logged in, say as "Kelly" when installing VB6.0 (and presumably at least some other packages), then when "Terry" logs in, VB 6.0 is fine, but the addins (which are DLLs in some cases) are gone!  There's a MSDN knowledge base article on this.
Neal HartmanAuthor Commented:
bhamilto had it right.
Neal HartmanAuthor Commented:
Your right.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.