Hi All,

I'm new to the forum....med programming experience.

I've built a database application in VB4.

It works fine in the VB environment.

As soon as I convert it to an EXE and install it on my PC at work - it stops working.

The first forum (password forum) opens.

after entering the username and password and clicking submit, I get a 'run-time' error - but no option to debug.

I can't figure out why it works fine at home and in the VB environment but not as an EXE. It also bothers me that there is no way for me to debug it.

I've been told that there is a particular DLL that is required in the Windows directory in order to run the EXE files. I have copied said DLL to my computer at work - but it didn't solve the problem.

I should also add that the EXE file works fine on my home PC but not my work PC.

Anybody have any ideas on how I can figure out what the issue is and fix it?

Thanis in advance!

-Mike

Hi All,

I'm new to the forum....med programming experience.

I've built a database application in VB4.

It works fine in the VB environment.

As soon as I convert it to an EXE and install it on my PC at work - it stops working.

You have to use the "Deployment Wizard" to create a setup file to install the program an another machine. Look either under Tools in VB or Start:VB.

Thanks WaltP - makes sense. My only problem now is that the Setup Wizard does not work. I get an error msg on launch and the application terminates. I found the BUG identifed on the microsoft website: http://support.microsoft.com/kb/170372 but I don't know what I need to change in the file. I tried "commenting" the Drive lines but it still didn't work.

Here's the code from the file mentioned on the site:

[SetupWiz-32]
Uses1=stkit432.dll
Protocol1=ncacn_ip_tcp,TCP/IP
Protocol2=ncacn_nb_nb,NetBIOS over NetBEUI
Protocol3=ncacn_nb_tcp,NetBIOS over TCP
Protocol4=ncacn_np,Named Pipes
Protocol5=ncadg_ipx,Datagram - IPX
Protocol6=ncacn_spx,SPX
Protocol7=ncadg_ip_udp,Datagram - UDP
Protocol8=ncacn_nb_ipx,Netbios over IPX
SetupProj=C:\vb4\setupkit\setup1\setup1.vbp
BootStrap=C:\vb4\setupkit\kitfil32\setup.exe
VBExe=C:\vb4\vb32.exe
RemoveInstallEXE=C:\vb4\setupkit\kitfil32\ST4UNST.EXE
Drive1=1.2 MB Disk,1213952,512
Drive2=1.44 MB Disk,1457664,512
Drive3=720 KB Disk,730112,1024
Drive4=360 KB Disk,362496,1024
[DAO2532.TLB]
Dest=$(MSDAOPath)
Uses1=DAO3032.DLL
[MSJT3032.DLL]
Dest=$(WinSysPathSysFile)
Uses1=VEN2232.OLB
Uses2=MSJTER32.DLL
Uses3=MSJINT32.DLL
Uses4=VBAJET32.DLL
Uses5=VBDB32.DLL
Uses6=MSRD2X32.DLL
Uses7=MSWNG300.DLL
Uses8=ODBCJT32.DLL
Uses9=ODBCJI32.DLL
Uses10=ODBCTL32.DLL
Uses11=VBAR2232.DLL
[DAO3032.DLL]
Dest=$(MSDAOPath)
Uses1=MSJT3032.DLL
Register=$(DLLSelfRegister)
[MSPX3032.dll]
Dest=$(WinSysPathSysFile)
Register=$(DLLSelfRegister)
[MSXB3032.DLL]
Dest=$(WinSysPathSysFile)
Register=$(DLLSelfRegister)
[MSXL3032.DLL]
Dest=$(WinSysPathSysFile)
Register=$(DLLSelfRegister)
[MSTX3032.DLL]
Dest=$(WinSysPathSysFile)
Register=$(DLLSelfRegister)
[CRYSTL32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
Uses2=CRPE32.DLL
Uses3=CRXLAT32.DLL
Uses4=u2ddisk.dll
Uses5=u2fdif.dll
Uses6=u2frec.dll
Uses7=u2fsepv.dll
Uses8=u2ftext.dll
Uses9=P2BDAO.DLL
Uses10=P2CTDAO.DLL
Uses11=P2IRDAO.DLL
Uses12=P2SODBC.DLL
Uses13=P2BBND.DLL
[COMDLG32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[DBGRID32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
Uses2=GRDKRN32.DLL
[DBLIST32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[GRID32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[ANIBTN32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[GAUGE32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[KEYSTA32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[MCI32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[MSCOMM32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[MSMAPI32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[MSMASK32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[MSOUTL32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[PICCLP32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[SPIN32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[THREED32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[GRAPH32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
Uses2=gsw32.exe
Uses3=gswdll32.dll
[MSLT3032.DLL]
Register=$(DLLSelfRegister)
Dest=$(WinSysPathSysFile)
[MSRD2x32.DLL]
Dest=$(WinSysPathSysFile)
Register=$(DLLSelfRegister)
[OLEPRO32.DLL]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
[COMCTL32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[RICHTX32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[TABCTL32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[SYSINFO.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[OCX Runtime Support-32]
Dest=$(WinSysPath)
Uses1=OLEPRO32.DLL
Uses2=MFC40.DLL
Uses3=MSVCRT40.DLL
[MSVCRT20.DLL]
Dest=$(WinSysPathSysFile)
[VEN2232.OLB]
Dest=$(WinSysPathSysFile)
[CTL3D32.DLL]
Dest=$(WinSysPathSysFile)
[MSJINT32.DLL]
Dest=$(WinSysPathSysFile)
[VBAJET32.DLL]
Dest=$(WinSysPathSysFile)
[MSWNG300.DLL]
Dest=$(WinSysPathSysFile)
[VBDB32.DLL]
Dest=$(WinSysPath)
[MSVCRT40.DLL]
Dest=$(WinSysPath)
[MFC40.DLL]
Register=$(DLLSelfRegister)
Dest=$(WinSysPath)
[VB Runtime 0409-32]
Dest=$(WinSysPath)
Uses1=VB40032.DLL
Uses2=ven2232.olb
Uses3=olepro32.dll
Uses4=msvcrt20.dll
Uses5=msvcrt40.dll
Uses6=ctl3d32.dll
[MSRDC32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
Uses2=MSRDO32.DLL
[MSRDO32.DLL]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Uses1=OCX Runtime Support
[VB4 Remote Client Support-32]
Dest=$(WinSysPath)
Uses1=AUTPRX32.DLL
Uses2=CLIREG32.EXE
[VB4 Remote Server Support-32]
Dest=$(WinSysPath)
Uses1=AUTPRX32.DLL
Uses2=AUTMGR32.EXE
Uses3=RACMGR32.EXE
[AUTPRX32.DLL]
Register=$(DLLSelfRegister)
Dest=$(WinSysPath)
Uses1=MSVCRT20.DLL
[AUTMGR32.EXE]
Register=$(EXESelfRegister)
Dest=$(WinSysPath)
Uses1=MSVCRT20.DLL
[RACMGR32.EXE]
Dest=$(WinSysPath)
Uses1=GAUGE32.OCX
Uses2=TABCTL32.OCX
Uses3=RACREG32.DLL
Uses4=ODKOB32.DLL
[RACREG32.DLL]
Dest=$(WinSysPath)
Register=$(DllSelfRegister)

I have no idea what any of that is. I just open the project and the deployment wizard makes a package of the executables and DLLs needed.

I get an error msg on launch and the application terminates.

gives no one any helpful information that can be used to pinpoint your problem. Even Shawn Spencer on Psych needs to see something useful ;)

deployment wizard doesnt work on XP for vb5 therefore i dont think the VB4 one will

So what's my next move to get this VB4 application installed on computers at work? I need this to be operational by the end of the week. Is there any other way I canmake this happen?

have you done something silly like pointed your app to a database at a certain path which then doesnt exist on other pcs?

you could try upgrading it to net maybe

deployment wizard doesnt work on XP for vb5 therefore i dont think the VB4 one will

Then why do they put it in VB? It's always worked for me... :confused:

[edit]Oops, come to think of it, I've never tried it on XP. Just NT[/edit]

vb4 and 5 package wizards just plain dont klike XP (or 98) - only ever worked for me on 95/NT - VB6 works just fine though

Anybody know of any other packager utility I can use for VB4 app on XP?

Hi Mike,

I use VB4 in XP Professional SP 2.

I agree with the posts that you need to have an installer...but bare in mind that (depending on which DAO you have written your app in) you may have DLL clashes anyway (with newer Jet engines installed with software at your work place). i am working through an issue like this at the momement with commercial software.

NB The VB4 SetupWizard does work on XP, but I have had the same problem that you had. Here's what I know:

1. Don't have your VB project in your 'My Documents'...because the Setup Wizard doesn't know how to read from there.
2. When my VB 4 Setup Wizard broke (didn't work) on my XP machine...it came back after either a system restore or I installed some software that replaced a missing DLL...anyway it came back.
3. You might try reinstalling VB4 to your home machine to see if the missing DLLs are replaced.

Best of luck with that.

If it's a small app..then I agree with the other postings...VB.Net Express is free on MS's web site...just use that.

regds
Vic
Viev Pty Ltd

This article has been dead for over six months. Start a new discussion instead.