By default, after opening a conection and doing some select statement, the odbc driver sets the transaction isolation mode to:
READ COMMITTED NO WAIT NO RECORD_VERSION
I checked this by query to the mon$transaction table.If a do some changes to any table the changes are commited automaticaly.
This mode is not suitable for us, because this blocks reads of changed rows by another computer. But if i change manually the transaction isolation level with the command:
SET TRANSACTION READ WRITE WAIT READ COMMITTED RECORD_VERSION
After doing this i need to commit evey change made on the database, if not commited the changes are lost after closing the connection.
I dont know whats happening but this is driving me nuts, can it be and odbc error?
I send to you an odbc trace file.