RE: Error 3197

Jerry,

I had very similar problems several years ago. Adding timestamps on all of the tables resolved the issue for me. The MySQL version we used is an older version. And, it is running through ODBC 5.1 as well.

Good Luck!

Ron


-----Original Message-----
From: Jerry Schwartz [mailto:[email protected]] 
Sent: Wednesday, January 05, 2011 10:35 AM
To: 'Al McNicoll'; [email protected]
Subject: RE: Error 3197

Well, that's ONE consensus. :-(

Another seems to be to add timestamps to all of the tables.

The problem with using SQL is that most of the forms don't use explicit code 
at all: they simply do what Access forms do.

I have to think about which event(s) to trap and which ones to cancel.

Regards,

Jerry Schwartz
Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032

860.674.8796 / FAX: 860.674.8341
E-mail: [email protected]
Web site: www.the-infoshop.com


>-----Original Message-----
>From: Al McNicoll [mailto:[email protected]]
>Sent: Wednesday, January 05, 2011 5:06 AM
>To: 'Jerry Schwartz'; [email protected]
>Subject: RE: Error 3197
>
>Hi Jerry,
>
>The consensus on the forums seems to be to replace the native DAO / ADO 
>Update
>methods with SQL Executes.
>
>e.g.
>rs.Open
>rs.FindFirst "ID = 24601"
>rs!TastesLike = "chicken"
>rs.Update
>rs.Close
>
>becomes
>con.Execute "UPDATE animaltable SET TastesLike='chicken' WHERE ID = 24601"
>
>I appreciate that this isn't always a simple rewrite, and I don't know 
>whether
>it's practical for your application, but it seems to have had more success 
>than
>other suggestions.
>
>See also: http://forums.mysql.com/read.php?65,44969,44969#msg-44969
>
>Kind regards,
>
>Al
>Integritec Limited
>
>
>-----Original Message-----
>From: Jerry Schwartz [mailto:[email protected]]
>Sent: 04 January 2011 22:22
>To: [email protected]
>Subject: Error 3197
>
>I've moved an Access 2007 application over to MySQL, using the ODBC connector
>5.1. When I try to update a record, as often as not I'll get a 3197. 
>Sometimes
>if I move back and forth in the table I can get around it, but I can't ask my
>users to go through various gyrations until they stop getting nasty messages.
>
>
>
>I've searched the web, and all I've found are complaints and suggestions that
>didn't work for me.
>
>
>
>I've tried toggling
>
>
>
>*         dynamic cursors
>
>*         return matched rows
>
>
>
>with no luck.
>
>
>
>In Access, all of the forms are designated to use Dynasets (inconsistent).
>
>
>
>Any suggestions? My job is more or less on the line.
>
>
>
>Regards,
>
>
>
>Jerry Schwartz
>
>Global Information Incorporated
>
>195 Farmington Ave.
>
>Farmington, CT 06032
>
>
>
>860.674.8796 / FAX: 860.674.8341
>
>E-mail:  <mailto:[email protected]> [email protected]
>
>Web site:  <http://www.the-infoshop.com/> www.the-infoshop.com
>
>
>





-- 
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:    http://lists.mysql.com/[email protected]


-- 
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:    http://lists.mysql.com/[email protected]