Access 2003 on 64 bit Windows? Routine or difficult?

[mat]

Does Access 2003 work ok on 64 bit vista? Has anyone tried it on 64 bit
windows 7? Are there issues finding odbc drivers for 64 bit versions of
windows? sql server,oracle, postgres are the main focus.

 

[Allen Browne]

Mat, I'm using Access 2000, 2003, and 2007 on the 64-bit version of Windows
7 (6.1.7600.) It's fine, though I'm using JET tables, so cannot vouch for
the ODBC drivers.

 

[David W. Fenton]

Does Access 2003 work ok on 64 bit vista? Has anyone tried it on
64 bit windows 7? Are there issues finding odbc drivers for 64 bit
versions of windows? sql server,oracle, postgres are the main
focus.

Your question is not entirely clear.

Do you mean Access as front end to an ODBC data source, or a Jet/ACE
database attached to a server instance?

If the former, what matters is having 32-bit ODBC drivers (I don't
know if there's such a thing as a 64-bit ODBC driver, but if there
is, Access (via Jet/ACE) won't be able to use it).

If the latter, it will only work if the server instance can use
32-bit ODBC drivers to attach to the Jet/ACE file.

There are reported problems from .NET programmers trying to utilize
a Jet/ACE data store on 64-bit Windows -- that scenario does not
work, from what I understand, but I expect that to be an issue that
is corrected at the point that Microsoft introduces a 64-bit version
of Office.

 

[mat]

Mmm your reply is not entirely clear! (but thanks <g>)

I'm not sure what you meant by Jet/ACE db attached to a server instance?
Do you mean from the sql server viewpoint, that it's linked to an Access
db? I've never even tried that, if that is what you're referring too.

I meant the #1 of your set of two, front end Access version whatever, on
64 bit windows, and using odbc linked tables to sql server, oracle etc.

I think there are 64 bit drivers, but if Access can't use them at this
point then 32 bit will suffice.

Between the two replies, sounds doable. Thanks to both of you.