VB6 Pro Controls damaged?

[DragonQ0105]

Hey, I'm using VB6 SP6 for my A-Level Project....I use Pro Edition at my college and Enterprise Edition at home.

However, the IT facilities aren't that good - when the rooms are booked, there is only one computer in the whole college with VB6 on it! (They won't buy more lisences or move the liscences from different comps). But, if I start a project using Pro Controls, or create a new porject with Pro controls, it gives a fatal error and asks if I want to send an error report...blah blah blah...

If I start a new "Standard EXE" Project it works fine. Are the Pro Controls damaged on this PC? The administrator here only works Mondays to Wednesdays for some reason, so I can't get him to look at it for ages (since he's always busy).

Is there something I can do that doesn't require a reinstall? (which I can't do since I'm not an admin) - I really need to work on this outside of the IT Rooms...

 

[bjd4jc]

I would start by trying to narrow down which specific cotrol(s) is causing the error. If you can get a standard exe to work, then add the controls 1 at a time until you get the error.

It sounds like one of the files is corrupt. If you find out which it is, you'll likely need to have it replaced, i.e. reinstalled. So, I would just put your name on the list and describe it as an urgent issue to your IT Admin.

 

[DragonQ0105]

Where can I find a list of files that are in Pro Edition Controls and not in the Standard EXE?

Even with Ent Edition Controls enabled (at home), there don't appear to be many ticks in the Control Components....are you sure the extra ones are actually listed there separately?

 

[CubeE101]

I agree, I usually start with the standard EXE, then add controls as needed...

Does the error occur after you have controls on the form and press run? or when you load the template?

If you do have controls on the form, what are they?

Visit My Site
PROGRAMMER: Red-eyed, mumbling mammal capable of conversing with inanimate objects.

 

[DragonQ0105]

When I load the template, it gets to about 10% of the way on the bar at the top, then gives the fatal error. Since it's the same place, I'd also assume it's one control...

But how do I track it down? As I said, each individual control isn't listed in the box, and I don't know which are Pro Controls and which aren't at home....

(Out of curiosity, why use Standard EXE then add controls? Does using Pro Controls take up more space?)

 

[bjd4jc]

There is a templates directory under the install location of VB6. In there you will find a project file. You can open that in notepad and then you will see the references that are added to the project file.

The Pro Control add a lot of controls to the form that you probably won't use in your project. I would reccomend starting with the standard project and then add controls as needed. If you're lucky, the control that is causing your problem won't be a control that you'll need to use in your project (-:

 

[jjames]

I pulled this from the VB Pro Edition Controls.vbp file. They are the controls added to a standard exe project when you use the Pro template. Open a standard exe and add these components 1 at a time...

tabctl32.ocx
msflxgrd.ocx
ComDlg32.ocx
mscomctl.ocx
mscomct2.ocx
msinet.ocx
RichTx32.ocx
MSChrt20.OCX
mswinsck.ocx
msmapi32.ocx
mci32.ocx
PicClp32.ocx
SysInfo.ocx
MSComm32.ocx
MSMask32.OCX
MSDatGrd.Ocx
MSDatLst.OCX
comct332.ocx
MSADODC.OCX
mshflxgd.ocx

 

[DragonQ0105]

The Pro Control add a lot of controls to the form that you probably won't use in your project. I would reccomend starting with the standard project and then add controls as needed. If you're lucky, the control that is causing your problem won't be a control that you'll need to use in your project."

Can't do that...the existing project uses Pro Controls....


What I'll do is copy the info about which controls I need from the template, then make a Standard EXE, copy them over one by one until I find the one that is causing problems...then not include it, and make a new Template.

Thanks

 

[HughLerwill]

DragonQ0105,

An idea that may work for you.
Backup the project vbp file then take a look at it with NotePad.
At the top are references then come Objects = ~~~.ocx these are the controls; delete the lines begining Object =.

Start up the project into the VB IDE and you'll be given messages that controls can't be found etc. A list of the unfound controls needed by your project will be written out to a log file for each form in your project. Put back the Objects listed in the logs.

regards Hugh

 

[DragonQ0105]

I tried to add them one at a time.... ALL of them (except COMDLG32.OCX) gave this error:

"Blah.OCX was not registerable as an ActiveX Component"

So, only one of the controls for VB6 Pro Controls Template actually works...

After looking on the internet, it seems I need to register the files with Regsvr32.exe via the Run Box...the particular machine doesn't have the Run Box (WINDOWS XP, Admin proabably disabled it to protect PCs).

So what now? Am I just gonna have to wait till next week and persuade the IT Manager for a reinstall?

 

[DragonQ0105]

(Sorry for double post):

New info - if I press OK in the Components Dialogue after enabling the COMDLG32.OCX File, I get the same error as I did before (Fatal error...send error report etc.).

So, if this is the file causing the probs, why do the others give the not registerable error?

Thanks.