Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MSFLXGRD.OCX ERROR 2

Status
Not open for further replies.

jadams0173

Technical User
Feb 18, 2005
1,210
I wrote and compiled an App in VB6 SP6 on a Win2K machine. I placed it on a network drive and machines running WinXP open the app fine.

I have encountered 2 pc's running win2k that when they try to open the EXE the following error message comes up:

"RunTime Error 339: Component MSFLXGRD.OCX or one of its dependencies is not correctly registered: a file is missing or invalid."

I check winnt\system32 and the OCX is missing so I d/l it from the internet and try to register it which gives the following error message.

"C:\WINNT\SYSTEM32\MSFLEXGRD.OCX is not an executable file or no registration helper is registered for this file type"

Can anyone offer any suggestions?
 
No ideas anyone...or did i post in the wrong forum?
 
I constantly have problems with flexgrids (and richtext boxes) on our corporate boxes. Sometimes copying the .ocx in and using regsvr32 works fine, and sometimes not.
When it doesn't, I've taken to simply installing the ActiveX portion of visual studio 6, and that has always solved the problem.
Sometimes reinstalling office fixes many controls.
Sometimes creating an install package from your project (Package & deployment wizard) will fix these problems, but not always.

It's always killed me how painful MS makes it to just run an app with some common MS control in it.
 
You can install the VB6 Runtime Library, which solves the problem in many instances.

-David
2006 Microsoft Valueable Professional (MVP)
2006 Dell Certified System Professional (CSP)
 
Thanks guys! I've been traveling the past few days and haven't been online. I will give the suggestions a try.
 
As Jasen stated, you just need to create a package and install it once. From that point on, as long as you don't add additional references, you can just do an x-copy installation. The setup program will copy all the needed dll's & ocx's to the clients computer and register them.
 
dglienna and maclead1021 thanks for the advice. I tried both methods with success!!! :) a star for each of you!!

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top