References for New Application Rollout

[BrokkenStik]

Hi.

I've developed an application in VB 5.0 for my department to use. This application will run from anywhere on my hard drive in spite of the fact that I hard coded the database path. I don't understand why it does. It seems to me that it shouldn't see the database file unless it resides exactly where I say it should.

Also, I copied the application and database onto another computer and it won't run. I suspect my references aren't on the test computer. I would imagine that all references are linked at compilation. How do I find out which references are missing on the computer I'm installing the application on?

I'll be installing this application on up to 50 machines ranging from Pentium to Athalon running mostly WinNT 4.0. I'm not aware of VB 5.0 having a packaging wizard. I know 6.0 does, but my department hasn't purchased it for me yet, as I'm an electronics engineer making a career change to software.

Any help is greatly appreciated.

Mark

 

[BrokkenStik]

I found the deployment wizard. Didn't think to start my search from the main menu.... Anyway, still having problems deploying this application to a test machine, but at least all the references are brought over with the .exe.

I'm also having problems finding the database once the install is run on the test machine. I've changed my source code so that the database resides in the same location as the application, which works on my machine but not on the test machine.

Any insights?

Thanks,

Mark

 

[BrokkenStik]

Will the strangeness never end?

I investigated my test computer, and it seems there is either a problem with the registry or the hard drive. My database was build in MS Access. When the application was first tested on the test machine, error messages showed a problem with the db connection. I installed MS Access from the LAN, but the problem persisted. Several hours later, I noticed that MS Access didn't show as being installed, so I installed it again. My application still showed a problem making the connection to the database, so I checked to see if the test computer had MS Access installed, which it didn't. Anyway, I'll submit a repair ticket for the test machine and find another test computer.

Hope these posts have at least been entertaining....