rwoosley
asked on
How do I get a system I developed with 32-bit Access to run with people running 64-bit Access
I've created a data reporting system using 32-bit Access with Basic background code but it will run on a machine running 64-bit Access.
If you have used any API calls, then you'll need two versions or use compiler directives. Also as Scott mentioned, controls and references all need to be 64 bit if your using 64 bit.
BTW, here is some helpful info if you did use any API calls:
This will help you determine what might need to be changed:
Microsoft Office Code Compatibility Inspector user's guide
http://technet.microsoft.com/en-us/library/ee833946.aspx
also read:
Compatibility Between the 32-bit and 64-bit Versions of Office 2010
http://msdn.microsoft.com/en-us/library/ee691831(office.14).aspx
and the section "Introducing the VBA 7 Code Base" for the general overview.
All the new 64 bit calls are here:
http://www.microsoft.com/download/en/confirmation.aspx?displaylang=en&id=9970
a list of all the calls that were modified for 64 bit:
http://msdn.microsoft.com/en-us/library/aa383663(VS.85).aspx
Jim.
BTW, here is some helpful info if you did use any API calls:
This will help you determine what might need to be changed:
Microsoft Office Code Compatibility Inspector user's guide
http://technet.microsoft.com/en-us/library/ee833946.aspx
also read:
Compatibility Between the 32-bit and 64-bit Versions of Office 2010
http://msdn.microsoft.com/en-us/library/ee691831(office.14).aspx
and the section "Introducing the VBA 7 Code Base" for the general overview.
All the new 64 bit calls are here:
http://www.microsoft.com/download/en/confirmation.aspx?displaylang=en&id=9970
a list of all the calls that were modified for 64 bit:
http://msdn.microsoft.com/en-us/library/aa383663(VS.85).aspx
Jim.
ASKER
Got it. I'll take a look at the Inspector. I also found your response to the same problem back in March of 2010. I'll check out both and get back Thanks!!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Got it, again. Good to know. It actually is not the client but a colleague on the ground that inadvertently (how I don't know) was issued a laptop configured to run 64 rather than 32-bit.
The part about the 2 development environments rings especially true. I will make the case to avoid this in the future using your strong arguments!
Thanks again.
The part about the 2 development environments rings especially true. I will make the case to avoid this in the future using your strong arguments!
Thanks again.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry it took so long to get back to this. I ended up having to give the uncompiled 32-bit Access 2000 version database to another colleague of mine to modify and (I'm assuming) test in his 62-bit Access environment. In any event, his modifications worked. He essentially removed all the background Access DECLARE statements and reworked a module that referenced them. I haven't had a chance to do a one-to-one comparison of the code but his mods worked. I tried using the Compatibility Inspector to no avail unfortunately. Thanks for the effort just the same.
You can't compile 32-bit Access apps to .mde/.accde and run them on 64-bit Access, however. You'd have to create two distinct versions - one for 32-bit, and another for 64-bit.