Solved

ODBC error when opening 32 bit query on 64 bit office

Posted on 2013-10-23
2
1,133 Views
Last Modified: 2013-10-23
Hi all,

We've just made a massive leap from office 2003 (32bit) to Office 2013 (64bit). Of course we have lots of problems now. One problem is that users are now getting an error when trying to open existing query files (.dqy file) that were created in excel 2003. It would appear that we can create new ones, but not edit existing.

I have tried installing the access runtime 64 bit but this doesn't work.

Anyway of getting round this?
0
Comment
Question by:MJB2011
[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
  • 2
2 Comments
 
LVL 57

Accepted Solution

by:
Jim Dettman (Microsoft MVP/ EE MVE) earned 500 total points
ID: 39593897
<<We've just made a massive leap from office 2003 (32bit) to Office 2013 (64bit).>>

 Well hate to be the bearer of bad news, but that probably was a mistake.   You should if at all possible stick with 32 bit Office.

<<One problem is that users are now getting an error when trying to open existing query files (.dqy file) that were created in excel 2003. It would appear that we can create new ones, but not edit existing. >>

 The problem is in general, everything you had was 32 bit and now needs to be 64.  That means:

1.  DSN's need to be created in the right place if you use them (there is an ODBC32adm.exe for 32 bit and one for 64 bit).
2. All drivers need to be 64 bit (ie. ODBC)
3. Calls to certain Windows API's will need have the PtrSafe attribute added.
4. Some Window API calls will need to be changed as they are different between 32 and 64 bit.
5. Any 3rd party DLL's, componets, etc will need to be changed.

On the flip side, the only thing 64 bit Office gives you is extremely large spreadsheets in Excel.   If you don't need that, then run, don't walk to 32 bit Office.

 Even Microsoft still recommends 32 bit Office.

Jim.
0
 
LVL 57
ID: 39593906
And just to be clear on this:

"Well hate to be the bearer of bad news, but that probably was a mistake.   You should if at all possible stick with 32 bit Office."

  32 bit Office or 64 bit Office will run under a 64 bit OS.   Just because the OS is 64 bit does not mean you need to run 64 bit Office.

 Also be aware that you cannot mix products within Office.  All either need to be 32 bit or 64 bit.   For example, you can't install Excel in 64 bit and Access in 32 bit.

Jim.
0

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

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

Access custom database properties are useful for storing miscellaneous bits of information in a format that persists through database closing and reopening.  This article shows how to create and use them.
My attempt to use PowerShell and other great resources found online to simplify the deployment of Office 365 ProPlus client components to any workstation that needs it, regardless of existing Office components that may be needing attention.
Learn how to make your own table of contents in Microsoft Word using paragraph styles and the automatic table of contents tool. We'll be using the paragraph styles in Word’s Home toolbar to help you create a table of contents. Type out your initial …
This Micro Tutorial demonstrates using Microsoft Excel pivot tables, how to reverse engineer competitors' marketing strategies through backlinks.

739 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