asked on

Failed to activate control vb.UserControl

I am testing an install of an app written in VB5 but renovated in VB6. The install runs fine and some of the app's functionality runs succesfully thereafter, but several elements generate a 374 error that reads "Failed to activate control VB.UserControl. This control may be incompatable with your application. Make sure you are using the version of the control that was provided with your application." Two questions (and I am not a VB person though I have basic familiarity with the language): 1. Is this something simple, like missing a dependent file in the install; or 2. am I going to have to go into the project and sort out the controls, etc. Any and all help is appreciated. - Mike

Bob Learned

What kind of controls are you using? Are they third-party controls or ones that you created?

Many controls are meant for target platforms, so they may not work when going from VB5 to VB6.

mikelanglais

ASKER

I didn't build the app, but I am reasonably certain there is a mix of 3rd party and custom controls. Much of the redesign was cosmetic and the previous version also used the same mix of controls.

If VB5 has never been installed. ( i.e New PC )
Copy ( to C:\windows\system ) & register ( regsvr32 msvbvm50.dll at the DOS prompt in System directory. ) MSVBVM50.dll, most others files are named the same.

If this fixes it, be sure to include it during the PD&W build.

ASKER CERTIFIED SOLUTION

Bob Learned

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

mikelanglais

ASKER

Thank you for all of your comments. We finally went with the "call the VB consultant" solution and sure enough, the thing now works. There were problems in a homemade component as a result from the 5 to 6 move. I am giving the points to TLO since he stuck with the question and I had already tried P1's idea before it was turned in. I know the rationale is lame given that both TLO and P1's suggestions were good, but I've gotta close this thing. Thanks again. Mike