Solved

ADO 32-bit/64-bit Incompatibility

Posted on 2011-03-10
10
1,773 Views
Last Modified: 2012-06-21
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.
0
Comment
Question by:TechMommy
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
10 Comments
 
LVL 75
ID: 35098678
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
 
LVL 85
ID: 35098829
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
 
LVL 11

Author Comment

by:TechMommy
ID: 35098839
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
Migrating Your Company's PCs

To keep pace with competitors, businesses must keep employees productive, and that means providing them with the latest technology. This document provides the tips and tricks you need to help you migrate an outdated PC fleet to new desktops, laptops, and tablets.

 
LVL 1

Accepted Solution

by:
PAGANED earned 500 total points
ID: 35098841
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
 
LVL 11

Author Comment

by:TechMommy
ID: 35098884
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
 
LVL 85
ID: 35099235
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
 
LVL 58
ID: 35099507
<<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
 
LVL 11

Author Comment

by:TechMommy
ID: 35099535
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
 
LVL 14

Expert Comment

by:Bill Ross
ID: 35472342
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
 
LVL 11

Author Closing Comment

by:TechMommy
ID: 35858011
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

Featured Post

Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

You need to know the location of the Office templates folder, so that when you create new templates, they are saved to that location, and thus are available for selection when creating new documents.  The steps to find the Templates folder path are …
This article describes a method of delivering Word templates for use in merging Access data to Word documents, that requires no computer knowledge on the part of the recipient -- the templates are saved in table fields, and are extracted and install…
Learn how to number pages in an Access report over each group. Activate two pass printing by referencing the pages property: Add code to the Page Footers OnFormat event to capture the pages as there occur for each group. Use the pages property to …
In Microsoft Access, learn the trick to repeating sub-report headings at the top of each page. The problem with sub-reports and headings: Add a dummy group to the sub report using the expression =1: Set the “Repeat Section” property of the dummy…

695 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question