Visual Basic Help

New computer axed a vbs3 PROGRAM

About a month or so ago I bought a new laptop. Just like my old laptop it's running XP Home SP2. I have an older program written in Visual Basic 3 to run in Win3.1-Win95.
When I run the program it will not perform file functions (load or save) in fact I don't even get the dialog box to choose name and location all I get is a small dialog that says "File not loaded" or "File not saved". All other aspects of the program seem to work as they are supposed to. I'm fairly certain it's not an XP problem because it worked fine on my other laptop which was more or less the same.
I haven't installed anything on the new system that I wasn't using on the old system.
The new computer is a Sony VGN-A690 with a docking station. I'm thinking this might be related to some pre-installed software or maybe the drivers for the docking station system.
I'm thinking something must be conflicting with vbx but I have no idea how to verify or track down the culprit. Ideas or suggestions would be greatly appreciated.
3,028 views 7 replies
Reply #1 Top
Just a wild guess here...
Do you think you might need the vbrun3 or 4 .dll file?
Reply #2 Top
I've got the runtime module version 3.0.5.38, as well as threed.vbx and cmdialog.vbx in the windows/system directory.
In the programs directory there are graph.vbx, spin.vbx, ssbc.vbx, threed.vbx and vbascrool.vbx
Reply #3 Top
So the program starts up and runs. It's certain functions that doesn't work? Have you tried running it in Compatibility mode? If you rightclick on the program's Exe (or shortcut) file, choose properties, there should be a tab labeled "Compatibility", Try setting it to a previous Windows version.
Reply #4 Top
Have you tried running it in Compatibility mode


doh.. forgot that one
Good call
Reply #5 Top
Yes I have tried setting it to Win95 compatibility - no go.
I looked into it a little further and it seems it's running under VDM, not sure if that may be involved but I'll keep trying.
Thanks for your input.
Reply #6 Top
Just wanted to update.
I got it fixed by excluding NTVDM.exe and WOWEXEC.exe from the Enhanced Dialog program. The main program used a graphic server porgram that was running under the Dos Virtual Machine. The most recent BETA of Enhanced Dialog caused it to bail on open and save dialogs. I'm not a programmer so I don't know the whys or hows but after four days of futzing with it there it is.
Reply #7 Top
Interesting. Thanks for sharing.