Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am currently investigating the possible issues when migrating from Windows XP 32bit to Windows 7 64-bit. The scope is MS Excel (32-bit), MS Access (32-bit) using VBA/Macros addins, ODBC and all related issues.

For example: if you use excel (32-bit) and oracle 32-bit odbc driver. There is an issue described at:

are there any (other) known issues / resources / websites / tools about this ?

share|improve this question
That's an error in the programming of the Oracle ODBC driver, since "(" and ")" are perfectly valid characters on Windows. That is, this is not a 64-bit issue at all -- the problem would occur on 32-bit Windows if you installed the ODBC driver in a folder with "(" or ")" in the name. – David W. Fenton Oct 26 '10 at 20:02
I agree that this is not directly related to 64 bit. But It does occur on a 64 bit windows system with office 32 bit installed, default in "program files (x86)". So in my opinion it is an issue occurring on windows 7 64 bit. You know any other issues ? and solutions. – Dre Oct 27 '10 at 7:07

I can't speak to Excel, but for Access, these are my links for 64-bit issues:

share|improve this answer
thx for the reply.addition: the scope is office 2007 (32-bit), so no 64-bit office. This is not an option. – Dre Oct 27 '10 at 7:10
There are no issues with 32-bit Office (or any other 32-bit apps) running on Windows 64-bit, so far as I know. The only place there can be issues is if your apps depend on outside components that won't run on 64-bit Windows. Out-of-box, there are no such dependencies in Office 2007. And so far as I know, it's pretty hard to break a 32-bit app under 64-bit Windows unless the app is doing the kind of stuff that is hardwired in a way that won't run inside the 32-bit subsystem. That would likely indicate a poorly-written program that should be replaced with something better. – David W. Fenton Oct 27 '10 at 20:42
Also, I wasn't even beginning to suggest using 64-bit Office. Had you read any of the links after the first, you'd know that. – David W. Fenton Oct 27 '10 at 20:43

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.