Printable View
Hey,
My company just bought me a Vista machine unfortunately. I have been writing all my apps in VB6 on my old XP pro machine. Now I am trying to open them up on my Vista pos and getting loading errors. I bassically narrowed it down to 2 components missing 1) Sheridan 3d controls and 2) vbAccellerator VB6 Grid control 2.0. Anyone know how I would get this stuff loaded on my Vista machine? I am ready to throw it through a wall.
The vbAccellerator thing is probably free, so you could go back there an download it again.
The Sheridan controls, however, are probably not free. Do you have the original CD that they came on?
I downloaded the .ocx from vbaccellerator and put it in my system32 folder and it still doesn't work. Is there a special way I should be registering it? I can't find any documentation.
Open up your VB project, click Project/Components/Browse
Browse over to that folder and double click on it.
That should make it a part of your project and register it. (At least it does in other OS's)
The file 'C:\Windows\System32\vbalGrid6.ocx' was not registerable as an ActiveX Component.
Vista is terrible.
I think, so the sake of your productivity, you need to get back to XP and your project, and perhaps persue this issue when the resolution isn't as critical.
Yeah that is probably what I am going to do... was just throwing it out there in hopes of someone already finding the answer. Been working on this app for over a year now... would be impossible to take out all of the references to these components. Thanks for the attempt tho!
Another thing that I just thought off....is there a "Contact Us" link on vbAccellartor that would put you in touch with the developers of this control?
It would be worth while, I think, to contact them and see if they have a solution, or, at least, log the issue with them.
Oddly enough I installed a package of the app that I made on the XP machine on the Vista machine and it did the registering of the components. Now they show up in the component window so I can select them.
I guess I can mark this semi-resolved =/
Including the Sheridan controls?
Installation will register the components, but many require a license file to be present in order to use the controls in design.
Can you now open your project, in design, and have access to them?
Yes all the sheridan controls are there now. I just tried opening another app that used winsock and for some reason it wasn't checked off in the component list but that was an easy fix.
I am still alittle skeptical to continue working on the vista machine with the experience I have had so far.
Do you have an XP machine, or is this the only box available to you?
I am actually typing this on the XP box. Got the Vista machine right next to it.
If you run into any oddities on our Vista box, be sure to post them. I'm certain many would be interested.
Thanks.
Also, make sure you run VB 6 as Admin or else you cant access certain features of it. Right click your shortcut or vb6.exe and select "Run As Administrator".
BTW Besoup, have you seen this FAQ?
Thanks for the link Hack, I think I am clear of all the issues listed there.
RobDog is there a way around having to right click run as admin everytime? I see how it is extra security for some but it gets annoying fast. :P
Yes, in your shortcut properties you can check the box for "Run as Administrator" and then save the change to your shortcut. Then each time when run via the shortcut it will run under admin credentials.
I got allot of that info in the link Hack posted but never got any credit from the poster. :( Oh well.
Rob: Perhaps an FAQ on some of the gotchas on running VB, itself, as opposed to an application made in VB, would be a good idea.
The tip you just posted for Besoup, as well as some of the others, could be very helpful to people like Besoup who are just getting into the Vista world.
Yeah any info on how to get the mouse wheel fix to work would be awesome too... getting DllRegisterServer failed with error code 0x80004005 when executing the run command.
Oh I have a bunch of stuff more still. :D I havent worked on fixing the mouse in the VB 6 IDE but we shall see how far I get with it.
* Vista FAQ to come *
I know this is a bit off topic, but, since you brought it up, I'll comment. (NOTE: This is pure speculation on my part.)Quote:
Originally Posted by Besoup
This will depend the driver you're using and whether the makers of that driver decide to upgrade it for Vista.
Remember VB6 came out in 1998 before wheels on mice were common. As such, VB didn't natively support a wheel. For the wheel to work in the VB IDE, the driver and related mouse software that needed to provide this functionality had to be developed. I would check the web site of your mouse manufucturer for specific Vista drivers and software, if any, that may provide. I wouldn't get my hopes up.
You may have a problem with ANY hardware older than just a couple years finding official support under Vista.
I have a newer MS Wheel Optical mouse and it needed special drivers for Vista. Even after I installed them still no wheel support in the VB 6 IDE. It does work in all other apps including .NET IDEs
To add to the frustration... when I step through code then stop the code, it crashes the IDE everytime... unbelievable.
Looks like it corrupted my project file because now it is crashing the same way on my xp machine...
Are you getting one of those memory errors?
I get a crash error on vista and on xp it just shuts down the program without any errors at all... think im gonna cry. :P
Did you copy the project to the Vista box, and then copy it back to the XP box?
(Do you have an XP backup of the project?)
Explain a bit more about "shuts down the program without any errors at all".
I am going to try to dig up a copy off my tape backup... tho it doesn't look very hopeful. It seems to only be happening in this one form I was working in so far. Basically I was trying to find a logic error in one of my routines so I inserted a break in the code. Then I just do the usual F8 and go through some variables. When I find what I am looking for, I hit the stop and my whole IDE disappears.
Does this happen on any other form, or just this one (hopefully)?
I've never encountered this situation before.
You can recreate the project file and add the forms that are good to it. Then for the one that is bad you can at least get the code out of it if you open the frm file in notepad or wordpad. The frx is the part with the binary resources which is probably corrupt.
Rob: Have you seen this behavior on Vista with respect to .frx files before?
yeah I am probably gonna try that when I get some time... unfortunately this app is huge.
Not on Vista but on XP I have.Quote:
Originally Posted by Hack
I think you are talking about Threed32.ocx which is a Sheridan 3d control. This is on the VB6 CD along with an extra reg file in the same folder. You can register it with regsvr32.exe Threed32.ocx. Then run the reg file will do an extra registration for this ocx. ;)Quote:
Originally Posted by Besoup
Just noticed that the .frx's are missing for alot of my forms... what's the best way to reproduce them? I am guessing new forms but there is like 20+ missing....
Try a little skullduggery.....delete a component that you have added to the form, then readd it, give it the name it had, and save the form.
no luck with the suggestion... thanks tho.
Did you run it afterward and use the forms in question?
yeah just tried that too... no luck.
Does your program seem to be not doing its job because of the missing .frx files?
nah the program seems to run fine... its just having problems in the IDE.
What kind of problems? The same that you were having with that one form?
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
If VB.NET is a requirment tell your people you need to go to a class.
Just created a new form and it doesn't even generate a .frx for it....
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.
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
Bang! :D
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?
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! :D
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.
Hmm, then that makes me think if its a CR issue. Whats on the other form that we were originally talking about?
On the other form there was a mshflexgrid, 2 ssoption buttons, 3 command buttons and a textbox.
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.
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.
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.
what kind of error logging would you suggest?
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.
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.
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.