|Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM ODBC Driver » View Thread|
|Messages 1 to 2 of 2 total|
|DBISAM 4.0 over ODBC write protect in Access 2010|
|Tue, Aug 13 2013 5:51 AM||Permanent Link|
Hi @ all
i want to open the Database over ODBC in Access 2010. That works fine but the problem is that everytime i make a change in the table it shows me the write-conflict popup.
I have tried it with marking the synch (timestamp) column without any marking, and all options in the odbc driver.
But everytime i see only this message that i can't save because any other user is using the table. With dbsys i can do all. But over ODBC only reading working.
My operating System is win8 64 bit. but have tested with win7 to and it haven't worked.
|Wed, Aug 14 2013 12:36 PM||Permanent Link|
Tim Young [Elevate Software]
Elevate Software, Inc.
<< i want to open the Database over ODBC in Access 2010. That works fine but
the problem is that everytime i make a change in the table it shows me the
write-conflict popup. >>
DBISAM has certain types of fields (Boolean and separate Date or Time field
types) that aren't supported in Access, so it can run into issues when a)
such a field is part of the primary key for the table and b) Access tries to
compare/search such fields during updates to determine which row to update
c) such fields are just part of the record and Access tries to compare them
as part of the process of determining whether a record has changed.
So, if you have a Boolean, Date, or Time field in your DBISAM table, then
you might see such problems.
If you have any other questions, please let me know.