Packaging Wizard Issue

[JoeCool71]

During testing my desktop application is working fine. I packaged the application and ran the exe file and the application still works fine. I also tested on various computers within my department and the application tested successfuly. When I install the application in another area of my company (they have older computers with less software) then I receive an error. The very first function in the application makes an ADO call and the error received is <Operation is not allowed when the object is closed> (Error 3704). I installed a current version of mdac_typ.exe and dcom95.exe on the computer in question and it still didn't work. I installed VB 6 on the computer to debug and after VB 6 was installed the application works. What dll's could the packaging wizard be missing???? Thank you for looking into this.

 

[CCLINT]

Now see if it still works when you execute the same EXE (with the IDE closed).

 

[JoeCool71]

I'm not certain I understand? From my understanding the IDE is the development interface (visual tools).

 

[CCLINT]

Maybe I mis-understood. You said that you loaded VB6 and the program worked - did you test this by loading the project and running it in the IDE or by running the EXE?

 

[JoeCool71]

I ran it both ways and the application works correctly after loading VB6. I'm at a loss... I've done a ton of research on the net, but I don't know what to do next.

 

[CCLINT]

Try installing the JET 4 update from the microsoft data site. Which ADO are you using? Did you also install any service packs for VB?
Does the developer PC where the EXE was created have VB6 Sp4 or 5?

For some reason the ADO recordset or connection object is getting closed early. Is the database local or on a server? If the latter, what type of server?

 

[THOMASNG]

I'm still quite new to creating .EXE's, but we initially
had a problem running them on computers whose .DLL's had
been &quot;upgraded&quot;. We finally had to instruct people not to
upgrade (which was OK, because these were special-use PCs).
I'm not sure if this helps.

 

[JoeCool71]

I installed VB sp5 and repackaged and reinstalled the application and I still ran into the same issue. I'm using an Access database as the back end and am using jet 3.5. Should I change the ADO to jet 4.0?

 

[CCLINT]

I would - if you want to stick with ADO. Change the references to ADO Recordset 2.5 library,ADO Data Objects 2.5 library and remove all other references to ADO and DAO, use MDAC 2.6 and download the latest Jet 4.0 sp. Re-compile, add MDAC 2.6 to the package and re-distribute.

 

[JoeCool71]

Well it finally works. Thank you for all of your help. Two minds are better then one.