ADO 32-bit/64-bit Incompatibility

I have been developing an application on 64-bit Windows with 32-bit Access for quite some time without problem. Until last week....Now, when I distribute the application to the users (who are running 32-bit Windows with 32-bit Access), any code that includes ADO blows up. If I open the database on any user's machine and change the ADO reference, all works perfectly. I know that I could fix this problem by changing to late binding, but this is not an option since there are hundreds of places where I use ADO.
LVL 11
TechMommyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
I wonder if this is related:

http://www.utteraccess.com/forum/Avoid-Windows-7-Sp1-t1962370.html

The content in that link came up in an MVP discussion recently ... and your situation sounds possibly similar ...?

mx
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
What do you mean by "change the reference"?

What are you doing with ADO? Are you just opening basic connections and recordsets? If so, then make sure to use the lowest version of ADO listed on your machine before deploying. This will (sometimes) help with that issue.
0
 
TechMommyAuthor Commented:
The information is helpful, but when I go to KB983246, I only see 64-bit downloads. The users' machines are all 32-bit Windows 7. Where can I get the fix for the 32-bit machines?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
PAGANEDCommented:
Windows 7 SP1 :  problem
.
ADODB references are changed when you update to the SP1 pack
.
http://social.technet.microsoft.com/Forums/fi-FI/w7itprogeneral/thread/7c20296f-6184-4c02-a616-2c6bd0bba3c9
.
When you complie your program on a  Win7-SP1 pack, only other WIN7-SP1 pack machines can use your program code that refers to ADODB
.
0

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
 
TechMommyAuthor Commented:
I am currently using Early Binding. I use ADO to execute stored procedures, passing them parameters. I also retrieve data using recordsets (primarily based on views).
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
You could use any version of ADO for that.

I'm not sure if the Windows 7 problem is your trouble or not, but it's worth looking into.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<I know that I could fix this problem by changing to late binding, but this is not an option since there are hundreds of places where I use ADO. >>

   And that would stink to because while it would work, late binding is a performance hit of 10-15% besides loosing intellisense when you develop.

   If you do need to change, Rick Fisher's Find & Replace would be helpful with that:

  www.rickworld.com

  Well worth it if you don't own it (and it's cheap too!).

<<You could use any version of ADO for that. >>

  I would try using an earlier version and see if it flies like LSM suggested.

JimD.

0
 
TechMommyAuthor Commented:
I tried using ADO 2.0 and the same problem occurred. I know that it's a Windows 7 SP 1 problem. If I compile an Access application using Windows 7 SP1, that application CANNOT be run on machines without SP1.
0
 
Bill RossCommented:
Hi,

I've had the same issue and went to a DAO solution.  I am trying to start a discussionj on this issue so you might look at this thread.

http://www.experts-exchange.com/Microsoft/Development/MS_Access/Q_26958211.html?cid=1416

Regards,

Bill
0
 
TechMommyAuthor Commented:
This did not solve my problem because the problem really doesn't have a solution. The "solution" contained a link to an article talking about the problem, and indicating that it hasn't yet been resolved. Just knowing this was helpful.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.