I have been linking MySQL tables into access for versions 3.23 thorough 5.17. The only way I have been able to deal with insert/update tables with a timestamp field is to build a query which includes all of the fields except the timestamp field. You can then do your insert or update against the query. ACCESS/ODBC does not know about the timestamp field so they are happy. If you specify CURRENT TIMESTAMP on the timestamp field in the MySQL definition, MySQL will populate the field every time the row is changed or a new row added.
> -----Original Message----- > From: C K [mailto:[EMAIL PROTECTED] > Sent: Friday, April 07, 2006 1:50 PM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; mysql@lists.mysql.com; [EMAIL PROTECTED] > Subject: Re: Reserevd Error -7776 -- Urgent > > I also tried folloing and got results as below: > 1) I updated the default for timestamp filed as CURRENT TIMESTAMP as > mentioned in MySQL 5.1 manual. > But this not worked. > 2) I dropped timestamp fiield from that table and refreshed link, then > I can ork properly. Now I can insert and update reocrds without any > problem. But this against the comment and responce from MySQL > community that it is necessary to have a timestamp field to properly > view and edit data in linked MysQL table. Else it will give he error > as #deleted, But isn't it strange that now it is not giving me any > such error. ? Why? > Thanks. > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
