December 1st, 2001, 11:18 PM
|
#1 (permalink)
| | Member
Join Date: Oct 2001 Location: NJ
Posts: 321
| Can't run my VB program on win2000...
A couple of years ago I created a program with Visual Basic 4...
The .exe file run fine on any win9x & NT machine as long as I included the files 'VB40032.DLL" & "Comdlg32.ocx" along with it.
I tried it on windows 2000 & didn't work....
Any ideas????
| 
|  | |
December 1st, 2001, 11:22 PM
|
#2 (permalink)
| | Misanthropic
Join Date: Oct 2001 Location: Bay Area, California
Posts: 19,310
|
Check Microsofts website, i'm sure they have some kind of patch or something to fix that.
| |
| | |
December 2nd, 2001, 06:06 PM
|
#3 (permalink)
| | Ultimate Member
Join Date: Oct 2001
Posts: 21,019
|
Is there anyway for you to recompile it on VB6 on a NT or Win2k box?
My guess is your DLL's are out of date and incompatible with 2k, Does it use ADO hmm wait you said VB4, or maybe DAO or RDO by chance? The MDAC has changed quite a bit in the past few years and some things maybe unsupported now...
If anything I have VB6 I maybe able to help if you still have the source...
After I re-read it your problem could lie with the Comdlg32.ocx common dialog controls. If your references refer to it in the system32 directory (this file comes standard) it will use the standard win2k activex control and there are most likely several incompatibilities.
Last edited by vass0922 : December 2nd, 2001 at 06:09 PM.
| 
| | |
December 2nd, 2001, 06:17 PM
|
#4 (permalink)
| | Member
Join Date: Oct 2001 Location: australia
Posts: 445
|
Microsoft didn't introduce a native code compiler into VB until VB5. VB4 apps were compiled to P-code, I don't really know what that means but maybe it has something to do with it. | |
| | |
December 2nd, 2001, 09:47 PM
|
#5 (permalink)
| | Member
Join Date: Oct 2001 Location: NJ
Posts: 321
|
Mmmm, I was thinking the same, maybe I need to recompile it on VB 6.....I'll give it a try & let you guys know.
Actually I tried that before but I think my .exe was bigger compiled with VB6 & it needed more libraries...since I was trying to keep it as small as possible I went back to VB 4.
I guess this time I've got no choice...I'll try VB 6 again.... | |
| | |
December 3rd, 2001, 12:18 AM
|
#6 (permalink)
| | Ultimate Member
Join Date: Oct 2001
Posts: 21,019
|
yeah unfortunately VB6 does startup with more references. However you may try to remove some of those references. I've never tried it, but hell couldn't hurt 
coughMUCHcough | |
| | |
December 6th, 2001, 10:58 PM
|
#7 (permalink)
| | Member
Join Date: Oct 2001 Location: NJ
Posts: 321
|
It worked!
I used VB 6 this time & I got a not-so-much-bigger .exe file
The wierd thing is that this time it doesn't need anything else than the "Comdlg32.ocx" file, it doesn't need any runtime library...
Ain't that strange....now the whole application is under a Mb....
So far I've tested it on win98SE, NT & 2000. | |
| | |
December 10th, 2001, 01:46 AM
|
#8 (permalink)
| | Ultimate Member
Join Date: Oct 2001
Posts: 21,019
|
it still needs that?
Hmm thats odd...
Thats the common dialog control.
maybe you're using something thats fairly new?
That has to be already included in the OS for windows, or you can't save documents, print, open documents...
odd.
You can't run it on a machine w/o that eh?
blows my mind lol | |
| | |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | | | 
Posting Rules
| You may post new threads You may post replies You may not post attachments You may not edit your posts
HTML code is Off | | | |   Most Active Discussions  | | | | | Recent Discussions  | | | | | 
|
hardware
prices 
