danblake
asked on
VB4 -> VB 5 Migration, Problem with VBX Control
Dear Experts,
I have a couple of with the .VBP Projects with the following lines in them:
VBX=..\..\..\..\..\WINDOWS
When I attempt to load them in VB5 (This is old code from VB4) I get an error and VB5 shutsdown (SP3).
I am looking to perform a migration from VB4 -> VB5 (To check for Win XP, prior to then migrating up to VB6 -> .NET etc..)
If I remove this line, I am able to open the VBP Project, but get the following errors on conversion:
Line 28: Class VBX.SSPanel of control Panel3D6 was not a loaded control class.
Line 42: Class VBX.SSCommand of control Command3D3 was not a loaded control class.
Anybody got any ideas ?
I have a couple of with the .VBP Projects with the following lines in them:
VBX=..\..\..\..\..\WINDOWS
When I attempt to load them in VB5 (This is old code from VB4) I get an error and VB5 shutsdown (SP3).
I am looking to perform a migration from VB4 -> VB5 (To check for Win XP, prior to then migrating up to VB6 -> .NET etc..)
If I remove this line, I am able to open the VBP Project, but get the following errors on conversion:
Line 28: Class VBX.SSPanel of control Panel3D6 was not a loaded control class.
Line 42: Class VBX.SSCommand of control Command3D3 was not a loaded control class.
Anybody got any ideas ?
Éric Moreau
Open your project in VB5. Go to Project->Components and add "Sheridan 3D controls". Close your project saving nothing but the .VBP. Reopen your project.
ASKER
The Sheriden 3D Controls come up as enabled.
(And I still get the above VBX Errors due to the removal of the VBX line from the VBP File manually)
I cannot open .VBP Project without removing the line:
VBX=..\..\..\..\WINDOWS\SY
(From within the file, is this correct ?)
If I add this back into the system, then this causes errors/bugs with loading in VB5.
(And I still get the above VBX Errors due to the removal of the VBX line from the VBP File manually)
I cannot open .VBP Project without removing the line:
VBX=..\..\..\..\WINDOWS\SY
(From within the file, is this correct ?)
If I add this back into the system, then this causes errors/bugs with loading in VB5.
VB5 definitely not supports VBX. The component I asked you to add is the OCX version you should use to upgrade. It worked for me in the past.
ASKER
Found what the problem is and have managed to put in place a solution...
1) VB5 does not like running under Win XP Hme. (Thought it might cause a few issues at is so old....
The removal of VBX = is required under Win XP Hme to get the system to load -- lots of errors/bugs running under XP -- crashs all over the place -- I really don't recommend it !).
Under VB5 & W98 the controls convert from VBX = to OBJECT = in the VBP project file and a big dialog box lets you know that it is going to convert the THREED.VBX Controls -> another part of the system. In XP This dialog box causes a crash to occur.
The line with VBX=THREED.VBX, should be replaced with:
Object={0BA686C6-F7D3-101A
Issue Fixed.
Points refund in progress ;)
1) VB5 does not like running under Win XP Hme. (Thought it might cause a few issues at is so old....
The removal of VBX = is required under Win XP Hme to get the system to load -- lots of errors/bugs running under XP -- crashs all over the place -- I really don't recommend it !).
Under VB5 & W98 the controls convert from VBX = to OBJECT = in the VBP project file and a big dialog box lets you know that it is going to convert the THREED.VBX Controls -> another part of the system. In XP This dialog box causes a crash to occur.
The line with VBX=THREED.VBX, should be replaced with:
Object={0BA686C6-F7D3-101A
Issue Fixed.
Points refund in progress ;)
That's what I told. Open the project, add the OCX and save!
ASKER
@emoreau...
"That's what I told. Open the project, add the OCX and save!"
It definitly was not as simple as this... the problem/bug was the migration was being done under Win XP, and the bugs would not allow the project to be opened properly under VB5/XP to allow you to open the project, add the OCX and save !....
This does not WORK under Win XP. I have detailed the fix for all others, on how you can just modify the .VBP File itself without requiring to load the system up under VB5 to prevent any errors in XP.
"That's what I told. Open the project, add the OCX and save!"
It definitly was not as simple as this... the problem/bug was the migration was being done under Win XP, and the bugs would not allow the project to be opened properly under VB5/XP to allow you to open the project, add the OCX and save !....
This does not WORK under Win XP. I have detailed the fix for all others, on how you can just modify the .VBP File itself without requiring to load the system up under VB5 to prevent any errors in XP.
The OS is not related to the issue.
You have to open the project, answering to continue to every message box that pops, add the component, save only the VBP, close and re-open.
You have to open the project, answering to continue to every message box that pops, add the component, save only the VBP, close and re-open.
ASKER
No -- The OS was definitly the issue in my case...
I'm suprised that you can tell me then when I cannot perform this on Win XP, and can on Win 98.
(Prehaps -- there are some drivers/other DLLs that are not making this possible on my Win XP install... but it is definitly a OS -> VB5 issue that I am experiencing !)
I can repeat the process on Win XP -- (I do still have the original file) and the whole VB5/SP3 will crash and cause problems, I can probably prove this via screen-dumps -- if only I had a good connection (e.g. Broadband) I would do this, just so you could see the issues I get with VB5.
The .VBP Project does not even open using VB5/SP1 or SP3 using Win XP without modifying the .VBP File prior to opening in VB5.
Threed has a .VBX Control which is present in the Win 98 O/S which is located in windows\system directory -- its part of the API interface... without this VB5 does not perform the conversion from VB4 -> VB5. (This is just what is happening on my Dual-boot installation..)
This is what I have found, you can tell me till you're blue in the face what should happen/work under Win XP -- I can PROVE this does not work on my machine: If you've got Win XP -- I'll even offer a Remote Assistance connection to verify this or why my XP Session in VB5/SP3 keeps crashing ?
I am happy to prove this issue.
I'm suprised that you can tell me then when I cannot perform this on Win XP, and can on Win 98.
(Prehaps -- there are some drivers/other DLLs that are not making this possible on my Win XP install... but it is definitly a OS -> VB5 issue that I am experiencing !)
I can repeat the process on Win XP -- (I do still have the original file) and the whole VB5/SP3 will crash and cause problems, I can probably prove this via screen-dumps -- if only I had a good connection (e.g. Broadband) I would do this, just so you could see the issues I get with VB5.
The .VBP Project does not even open using VB5/SP1 or SP3 using Win XP without modifying the .VBP File prior to opening in VB5.
Threed has a .VBX Control which is present in the Win 98 O/S which is located in windows\system directory -- its part of the API interface... without this VB5 does not perform the conversion from VB4 -> VB5. (This is just what is happening on my Dual-boot installation..)
This is what I have found, you can tell me till you're blue in the face what should happen/work under Win XP -- I can PROVE this does not work on my machine: If you've got Win XP -- I'll even offer a Remote Assistance connection to verify this or why my XP Session in VB5/SP3 keeps crashing ?
I am happy to prove this issue.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.