Error During application setup while registering MSRDC20.OCX in VB5.0

When either manually registering all ocx's or even using VB 5.0's setup utility, we are having a problem registering
the RDO 2.0 control (ocx) for the application developed.  In both cases, using the setup program or manually
registering MSRDC20.OCX it will not register on the clients machine.

This is our first attempt at deploying a VB5.0 and SQL server 6.5
application.  Any help would be appreciated.

rwp9350Asked:
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.

ksleungCommented:
Does it only happen to the MSRDC20.OCX? How about other controls?
0
rwp9350Author Commented:
All other controls seem to register correctly, when using the vb setup disks utility even it had a problem in registering MSRDC20.OCX.  Of course when you try to fire up the application a message box appears to tell you that the RDO control is not correctly registered.
0
rwp9350Author Commented:
I have upped the number of points in order to get this solved.
0
ChizlCommented:
You have a currupt OCX file..   Email me and I will tell you where to get it..  (chizl@cyberdude.com and gavin1@airmail.net)   Then you need to run the setup wizard again to create new setup diskettes.  That should fix your problem..
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
rwp9350Author Commented:
I believe that Chizl had a good answer, but it doesn't look like it is the problem.  In trying other things yesterday, on the test machine we have, it hasn't had any office 97 product loaded on it yet.  In comparing my machine and another test machine that the VB5 application does work on I noticed in the registry there were several entries for the MSRDC20.OCX in several folders named InProcServer32 where the OCX was registered.  In addition, there was another entry in the Shared software section for the OCX.  

On the test machine that would not register the OCX there was no entries whatsoever.  I then installed Access 8.0 and immediately tried to run my app and it worked!  I then checked that machines registry and the MSRDC20.OCX and MSRDO20.DLL registered correctly.

Bottom line, it appears to me to be a bug with the OCX and DLL in not self-registering themselves as they should by creating the proper registry entries.  Otherwise, the workaround is to have an Office 97 product installed on the client machine until Microsoft corrects the bug.
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
Visual Basic Classic

From novice to tech pro — start learning today.