Re: ODBC to MySQL

[William Underwood <wllmundrwd@charter.net>]

> From: "L. V. Lammert" <lvl@omnitec.net>
> Date: 2005/01/20 Thu PM 04:39:29 CST
> 
> At 04:20 PM 1/20/2005 -0600, you wrote:
> >It sounds like you're using Access as your ODBC client. Access does all 
> >kinds of things in addition to what a barebones ODBC application might.
> 
> Unfortunately, yes.

Access sucks(!) as an database frontend.  Don't know the technical details, but after much testing (both with 97 and 2000), it seems like it doesn't access the table until it see's a query, and then, instead of passing the query off to the db engine, it sucks the entire table(s) down to the local system and runs the query on it's own.  Once you have your Access app written, migrate to a VB app; the VB database interface actually does pass the query off to the db engine...

If you would like to confirm this, build the same table in Access, then run the that query/form against it, while watching Access's RAM use.  Then run the query/form against the ODBC connection, and you'll see the RAM use go significantly higher than just the straight Access version...

Freakin' POS Access...

>          Lee

HTH,
William


--
William Underwood
wllmundrwd@charter.net


-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.