Problem with exe

[iamtiger]

I recently developed an application using VB6 & Access 2000 using jet 4.0 and ADO 2.5. The program works fine on the computer that I used to create it, but when I transfer the exe file to a computer that does not have VB or Office it does not work. Could it possibly be because I am using jet 4.0 or the fact that the 2.5 object library is not on that computer?

[kleagle]

i guess so too.
try using the package and deployment wizard to install your application into another machine, that wil ensure that all necessary components are included with the exe.
or you can simply go to reference and check out what object and library you had included and manually copy them to the foreign machine. but you will have to register all of them first before you run your exe.

rgds.

KT

What problem/error message did your application gave?

[iamtiger]

Here is the problem that I am having: the program begins to load, but when it begins to load the mdi form that includes accessing the database it just closes with no error messages and the mdi form never shows up!

Thanks for your help

Chris

If the computer I am using does not have the current MDAC library that I am using, (2.5) could that be the problem? If so how do I install it on the computer if I am trying to ditribute the application?

[kleagle]

from what I know, it does make a different because you are using ado. it is like opening a word 2000 document using notepad or word 6.0
look for mdac_typ.exe in your visual studio's sub directory and run it in the other machine, and it will install the mdac version which is compatible to the program you compiled.

rgds.

KT

If the other machine is not having MDAC then that dosen't makes any difference. All u have to do is to check if all refrences u have made is been closed properly to free up the computer resources..
Using the Package and Deployment Wizard include all other dlls and files necessary for the application to run..
Raise errors in ur application so that
u may come to know which part of prog is
having problem.

I have never expierenced any problem while distributing the VB application. I think there's no need to install the MDAC on the other machine. The Package and Deployment Wizard does it all for you....

[kleagle]

but he just mentioned that he is using ado. isnt that related to mdac?
I could be wrong. :>

KT

[iamtiger]

Once I installed MDAC 2.5 on the other computer, the program worked fine. I realize that a package and deployment with 2.5 should make it work after installing the program. Thanks everyone for your help.