[DB-SIG] connecting to an access database...

M.-A. Lemburg mal at lemburg.com
Thu May 8 13:57:11 EDT 2003

Marcos Sánchez Provencio wrote:
> You may try using COM+ADO or COM+DAO (or ActiveX or whatever the name
> is) to access Access. I believe DAO is also a native api for Jet
> databases.

I believe that's what MS wants you to think :-) If you scan the Jet
Engine DLLs though, you'll find lots of ODBC APIs in there. ADO/DAO,
.NET or whatever they've come up with recently simply adds a few
layers on top of the ODBC API these DLLs expose.

BTW, I'd suggest to have a look at MS Desktop Engine (MSDE) 2000;
basically MS SQL Server 2000 without the GUI tools). That's certainly
a powerful alternative to the Jet engine used in Access.

> ¿Is there any performance comparison? I suspect the best
> option is mxODBC if you need support or are planning to migrate from Jet
> to more serious db servers.
> The odbc module from win32all must be a dinosaur now, but it may work
> for you...
> El jue, 08 de 05 de 2003 a las 10:19, ali escribió:
>>is there an api that connects directly to an access database without using
>>much like kinterbasdb to firebird...
>>(am i correct in my "parallelism"... anyway :)
>>thanks again....
>>DB-SIG maillist  -  DB-SIG at python.org

Marc-Andre Lemburg

Professional Python Software directly from the Source  (#1, May 08 2003)
 >>> Python/Zope Products & Consulting ...         http://www.egenix.com/
 >>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
EuroPython 2003, Charleroi, Belgium:                        47 days left

More information about the DB-SIG mailing list