Jake Yazici wrote:
> To verify that this simply wasn't a DAO problem, I
> created another test app using only ADO for row
> inserts on a couple of the migrated tables. The
> environment configuration is the was the same
> (MySQL table mapped to linked table in Access2K,
> using VBA ADO lib 2.6). Again, the row was
> inserted to the MySQL table, but the auto_inc PK
> value would not return to the recordset object.
>
> I re-linked the tables to their MSSQL
> counterparts, and the inserts worked as expected,
> and returned valid record ids. For me, this really
> narrows it down to the ODBC driver. Does anyone
> have any suggestions (other than wait for
> Connectort/ODBC 5.0)?
>
> Is there a specific bug # for this?
Jake,
Older versions of MDAC seem to break a lot of items w/ Connector/ODBC. Is there any way you could upgrade to MDAC-2.8 (you're on 2.6) and see if this issue goes away?
-Mark
Mark Matthews
Consulting Member Technical Staff - MySQL Enterprise Tools
Oracle
http://www.mysql.com/products/enterprise/monitor.html