Re: ODBC DRIVERS FOR ACCESS, EXCELL ,ETC



These drivers (Access, Excel) are only available for the 32 bit mode; so you
must use the 32 bit version of the ODBC administrator that you will find at
« Windows\syswow64\odbccad32.exe » and these dsn will only works for
programs running on the emulated 32 bit platform (WOW64) of the Vista 64
bit.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"George" <George@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1DEAD520-246F-41AB-B90B-E1C4B2F276DD@xxxxxxxxxxxxxxxx
My new hp laptop installed with visa ultimate 64bit has no drivers for
access
or excel and I need to use an application that connects to an access
database
through an odbc connection. How do you install drivers into the odbc
administrator for access or excel. The only driver is for sql server. I
have
installed mdac 2.81 thinking this would work but it dit not. Any
assistance
will be appreciated.
--
GeorgeV from Phoenix, AZ


.



Relevant Pages

  • Re: Excel ODBC drivers
    ... Microsoft points me at third-party sites the appear to be ... I'm not happy about that seeing as Excel used to have the ... Any suggestions for free ODBC drivers that'll work with Excel on OS X? ...
    (uk.comp.sys.mac)
  • Re: Excel ODBC drivers
    ... I'm not happy about that seeing as Excel used to have the ... necessary on the install disk. ... Office 2004 didn't come with ODBC drivers either. ...
    (uk.comp.sys.mac)
  • Re: Excel ODBC drivers
    ... I'm not happy about that seeing as Excel used to have the ... Office 2004 didn't come with ODBC drivers either. ... I've got a PostgreSQL database running on a Linux server. ...
    (uk.comp.sys.mac)
  • mac os x Excel odbc text driver
    ... and use them in pivot tables. ... suitable text drivers for odbc. ... Older versions of Excel had text drivers ...
    (microsoft.public.mac.office.excel)
  • Re: C0000005 errors: ODBC driver problem?
    ... Your suggestion to use APPEND FROM solved the problem. ... There must be a bug in the Excel ODBC driver I was using, because when I entirely stopped using SQLConnectand SQLexecfor Excel and instead used ...
    (microsoft.public.fox.programmer.exchange)

Loading