-----Urspr�ngliche Nachricht----- Von: Olaf Doschke [mailto:[EMAIL PROTECTED] Gesendet: Montag, 23. August 2004 12:29 An: [EMAIL PROTECTED] Betreff: linked tables in Access 2003
Repeating what I posted with a wrong subject: Hi everyone, If I add a MaxDB table to an Access2003 mdb as linked table and open the datagrid for direct input everything works fine up to the point where I want to change some data :o). I get a "write conflict" message, although I'm definitely the only user on that MaxDB test database. SQL trace log gives no hint: If I change the logs output file while I have the linked table open and before any changes, no further logging happens, when I change same data. So I don't even know what Access tries to do, when giving me the "write conflict message", probably some record locking. Config: Server: MaxDB 7.05.00.08 Database (Unix) on Debian linux. Client: Windows XP 2003 SP2 (the same behaviour on SP1) Access2003 ODBC-Driver 7.05.00.07 from 20.11.2003 (sqlod32.dll) To be more exact: ODBC VERSION : 7.5.0, BUILD: 007-113-057-319, which is the newest ODBC-driver I found. ODBC settings: INTERNAL Uncommitted I also tested other isolation levels with no success, but uncommitted should make the least problems concerning locks. If I use the same DSN I can get a remote view working perfectly with MS Visual FoxPro 7/8, which is writing back changes via UPDATE-SQL with no problems. SQL queries themselves from Access are also unproblematic. Using a DSN on a MS SQL Server also does not show this erroneous behaviour. Any hint on using linked MaxDB tables in Access? With kind regards, Olaf Doschke -------------------------------- Setmics Schroetteringksweg 16 D-22085 Hamburg Tel. : +49 (040) 64 78 92 - 28 Fax : (040) 64 78 92 - 31 eMail: [EMAIL PROTECTED] Web : http://www.setmics.de -------------------------------- Hello, if I remember right I had the same problem. My configuration was Access 97/2000 with SapDB 7.4. Do you have a timestamp-column which is filled by MaxDB? On my side I could solve the problem by filling my timestamp-column through Access (now()-function). It seemed to be a problem with the milliseconds. Now I only have an exactness of one second, but this works for me. Hope that helps Peter -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
