Hello, I had the same problem and I solved it by not using the SAPDB-Timestamp. I use a field which is filled by Access (i.e. the 'now'-function). After that I didn't run into this problem anymore. My opinion is that the timestamp-field (SAPDB) is to precise (up to miliseconds) for Access; a Access timestampfield is only up to seconds.
Hope that helps Peter -----Urspr�ngliche Nachricht----- Von: Mark Thomas [mailto:[EMAIL PROTECTED] Gesendet: Montag, 26. Januar 2004 23:20 An: [EMAIL PROTECTED] Betreff: Timestamp field, Windows 2000, and ODBC--weird problem. I'm having a strange problem with Timestamp fields on SAPDB 7.3.0.40 and 7.4.3.27. We have a table that contains a timestamp field. This table is linked by ODBC into Access 97. When a Windows 2000 system tries to update any field in the table, Access reports that someone else has been trying to update the record and rejects the update. Our Windows 98 machines don't encounter this problem. This occurs even when the timestamp field is not being updated--any update to any field causes this problem, as long as the timestamp field is present. If I remove the timestamp field, the problem disappears. Does anyone know what might be causing this? Thanks. -- Mark Thomas United Drugs -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
