How do I fix an ActiveX Common Dialog Control registration problem?

I am trying to register a simple ActiveX control through MS-ACCESS 97 running under Windows 95 and am having trouble with it conflicting with an already registered control.  Using the References selection from the Tools menu, I can determine that "Microsoft Common Dialog Control 5.0" is MISSING.  So I use the browse button to locate Comdlg32.ocx in the c:\windows\system folder and click Ok to register it.  The MISSING status does not change.  When I use the ActiveX Controls menu selection to try to register the control, there is already a listing for "Common Dialog Control" but it does not show a path/filename listing at the bottom of the window when it is selected.  If I select this listing and click register, how do I know which .ocx file belongs to it.  I tried registering it as c:windows\system\comdlg32.ocx but that doesn't cure my problem.  When I select it and try to unregister it I get an error saying the control cannot be unregistered and that I need to use the application's setup program.  But I don't know what that is.  I am running the same MS-ACCESS database on another PC and it works fine.  When I look at the ActiveX Control Registrations, "Microsoft Common Dialog Control 5.0" is registered as c:\windows\system\comdlg32.ocx and I do not see a listing for "Common Dialog Control" at all.  I have tried copying the OCX file from the PC that works to the PC that does not but can not seem to get it to register properly.  Are there more files than just the comdlg32.ocx involved here?  Can someone tell me how to get this ActiveX Control registration issue solved?
gwbrittAsked:
Who is Participating?
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.

JimMorganCommented:
gwbritt:

Welcome to EE.

I believe that what you are having a problem with is the Common Dialog Control.  There could be two reasons for this.

Did you recently install VB6 or Access 2000?  They use a different Comctl32.ocx which is not compatible with Access.

The latest version of Comctl is 5.0 (sp2) and there is more than one (sp2).  This is also a program which other programs provide as each one may use a slightly different version.  A poor installation program from one might have overwritten the one in you system directory without properly registering it.

Go on the Microsoft site and get the latest version of Comctl32.ocx.  The date I have on mine is 6/24/98.  We had a lot of problems copying Access apps to different systems and it making this complaint.  Since you are running the app on another PC, it sounds as if the app might have been created on that computer and so is looking for a later release than the one on the problem computer.

We tried various releases of the activex and found that this was the only one that we could find that worked on any Windows computer.  It supposedly is backward compatible with all other versions of the control.

I would also suggest that, if you can get one, to upgrade Access to 97.  There is a lot of improvement between the two versions and compatibility is one of them.  If you do upgrade, be sure that you have all the latest service releases and packs for 97.  See http://www.experts-exchange.com/Computers/Databases/Access/Q.10217158.html for information about the latest versions.

Jim
0
gwbrittAuthor Commented:
Edited text of question.
0
gwbrittAuthor Commented:
I follow what Jim is saying about versions, etc. and think that is related to the issue.  I made a mistake in my original question where I said I was using ACCESS 95 and so he correctly pointed me towards 97.  However, I am actually using ACCESS 97 but running under Windows 95.  I have edited my question to reflect that.  My real concern is not being able to unregister the version of the Common Dialog Control that is presently registered.  I feel like if I could do that, I could get the proper version installed and registered.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

JimMorganCommented:
The problem you may be having with your Windows 95 common dialog control is the version of IE you are using.  Windows 95 came with either IE3 or IE4.  IE3 is a real problem when used with Access.  IE4 needs to be updated to 4.02 I believe.  This will update the ComDialog control.  Upgrading to IE5 will definitely bring you up to date.

The only thing else that you might be able to do is go into the registry and manually remove the old registry information for the common dialog control loaded.  I don't advise doing this because a lot of Windows functions depend on the control.

Jim
0

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
gwbrittAuthor Commented:
I have solved my original OCX control problems and thanks partly to Jim's answer(s).  It turned out I did new a newer version of the OCX and I did need to get it from the MS download site.  However I pretty much had to figure out on my own the exact sequence of steps to install, unregister and then register the new version of the control.  I appreciate Jim's response as it got me refocused on the right track.  I sure wish MS documentation of OCX installation and registration was better.
0
JimMorganCommented:
I'm glad that I got you re-focused.  You usually don't have to uninstall or unregister the old OCX control.  Some of them are being used by Windows and part of the registration process of the new OCX is to do a warm-reboot and unregister the old version.

You are right.  MS does a miserable job of telling you how to deal with ActiveX controls.  I believe that they figure if you know enough that you know that you need one, then you probably know enough to muck around with the registry on your own.

That is about the same level of logic as saying if you can change the spark plugs in your car, you should also know how to time the engine.

Jim
0
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
Microsoft Access

From novice to tech pro — start learning today.