[Semi-RESOLVED] Vista and VB6.0 Components issue...

[Hack]

Does your program seem to be not doing its job because of the missing .frx files?

[Besoup]

nah the program seems to run fine... its just having problems in the IDE.

[Hack]

What kind of problems? The same that you were having with that one form?

[Besoup]

Yes the IDE crashing when I am done stepping through code and hit the stop button... only seems to happen on certain areas.

gonna have to learn VB2005 with a quickness :P

[Hack]

If VB.NET is a requirment tell your people you need to go to a class.

[Besoup]

Just created a new form and it doesn't even generate a .frx for it....

[RobDog888]

Did you place any images on it? If not then a frx wont be generated as its only for graphics. The controls are not graphics and are in the frm file.

[Besoup]

yeah I just did a restore from an old tape backup and realized they all didn't have .frx before. So now I am guessing it is just a corrupt .vbp which can't be fixed on Vista due to MS's lack of support. So I am thinking that I am left with 2 options... either live with the constant crashing or throw another partition on this PC and load XP and rebuild my .vbp.

shoot me :P

[RobDog888]

Bang!

Well its just down to the one form now isnt it? Di you try my suggestion about creating a new vbp in a separate folder and copying over the forms and modules cand classes and adding each one, one at a time?

[RobDog888]

Also, if there is no frx for the form then its possible to open the frm in notepad and copy out the code as its nothing more then a text file. Then create a new frm file (like when recreating the project as suggested in the previous post) you can paste it in and viola!

[Besoup]

Yeah I tried making a new .vbp and importing all of my stuff. When that didn't work I deleted the suspect form and copied the code into a new one and it still produced the same problem. I haven't tried rebuilding it on a XP box yet... that would be my next option. Unfortunately it isn't only one form like I thought... I have another form that has a crystal report viewer control on it that I preview all of my reports on. Whenever I preview a report then exit the program normally when running it from the IDE it crashes the whole IDE.

[RobDog888]

Hmm, then that makes me think if its a CR issue. Whats on the other form that we were originally talking about?

[Besoup]

On the other form there was a mshflexgrid, 2 ssoption buttons, 3 command buttons and a textbox.

[RobDog888]

Can you paste the code in a new file but do it one control at a time. You know that code that is in the beginning of the frm file that specifiles the controls properties on the form? Maybe you can find the offending control that way.

[Besoup]

That form only crashes the IDE when I step through the code and has no problem when I run it. I can't really do one control at a time and step through anything because most of the controls are tied into the grid populating sub which is the one I found the problem in. I am gonna go try to step through another subroutine in that form.

[RobDog888]

Perhaps adding some error logging so you can find the procedure that is crashing it. Then you may be able to determine the code or control.

[Besoup]

what kind of error logging would you suggest?

[RobDog888]

Just some On Error GoTo statement at the top of the most obvious procedures. In the error sub just write out to a textfile or use the App.LogEvent method to write to the system app event log.

[Besoup]

Found a couple events in my event log that are generated on each crash:

Faulting application VB6.EXE, version 6.0.97.82, time stamp 0x403acf6c, faulting module VBA6.dll, version 6.0.0.9782, time stamp 0x403ad081, exception code 0xc0000027, fault offset 0x0017ccd5, process id 0x3e4, application start time 0x01c78ce7bb081003.

Faulting application VB6.EXE, version 6.0.97.82, time stamp 0x403acf6c, faulting module usp10.dll, version 1.405.2416.1, time stamp 0x3a56a9b2, exception code 0xc0000005, fault offset 0x00029b73, process id 0xe5c, application start time 0x01c78cd39dd362bd.

[RobDog888]

Yes but those are not specific enough as vb6 loggs it when your app that is running inside it crashes. You need to log your own or write a log file.

[Mivoat]

I've just had the same problem and solved it.

The the key to it was Error: faulting module usp10.dll, version 1.405.2416.1 .

Do a file search for usp10.dll an you'll find an ancient version of usp10.dll in a Crystal folder (view Properties -> Details) . Replace it with a newer version.

[Keithuk]

I know this is an old topic but I will add my two pence worth.

The Sheridan 3D (Threed32.ocx) is an old ocx that used to be used with VB5, its still available on the VB6 CD, search.

If you can't find vbalGrid6.ocx from VB accelerator then its used with Malwarebytes but its in the C:\Program Files\Malwarebytes' Anti-Malware folder and it does register. You could try copying it to the Windows\System32 folder and register it again. I can add vbalGrid6.ocx from the C:\Program Files\Malwarebytes' Anti-Malware folder and it shows on the Toolbox and works.

All of these work on my Vista.