AFAIK, it cannot be done.

>
>I wasn't sure where to ask this question, but I thought some people here may have bumped into this already.
>
>I'm dealing with a legacy app where users are slowly moving into the 64 bit arena. I've been dealing with 64 bit for a while now so I know the difference between 64 bit ODBC and 32 bit ODBC and using the SysWOW64 folder for 32 bit ODBC, etc. But today I've hit upon a new problem.
>
>I'm supporting a legacy MS Access 2003 app that, amongst other things, uses ODBC connections to get to some VFP data. This has worked fine for 32 bit systems, and for 64 bit systems as long as I set up the 32 bit ODBC connection under the SysWOW64 folder.
>
>But now, MS Office 2010 is on the horizon and some of these users will be going to 64 bit MS Access. So I've downloaded the MS Office 2010 beta to test this out. Unfortunately, the installer will not let you have you have a 32 bit version of office installed on the same machine as a 64 bit version of Office 2010. So after I remove the old 32 bit version (Office 2003) and reinstall the new 64 bit Office 2010, the 32 bit ODBC connection appears to be not usable by the 64 bit MS Access.
>
>Am I dead in the water with this combination? Or is there a way to have 64 bit MS Access talk to a 32 bit ODBC connection?
>