Refresh aplication using Delphi7+Firebird1.5
hi , people
I'm developing a application Client/Server.
The Database (FireBird) is Located in the Server. And the Clients is working in machines in the same network.
Problem: The Inserts only is visible in the local client, and other client don't view the modifications, It's visible if client restart the program and reopening DataBase.
I'm using IBX components (IBTable, IBQuery).
I tried to use "Table.Refresh" OR ("Table.Close" / "Table.Open") but this solutions not worked.
Somebody knows if exists some solution for this problem.
Thanks...
I'm developing a application Client/Server.
The Database (FireBird) is Located in the Server. And the Clients is working in machines in the same network.
Problem: The Inserts only is visible in the local client, and other client don't view the modifications, It's visible if client restart the program and reopening DataBase.
I'm using IBX components (IBTable, IBQuery).
I tried to use "Table.Refresh" OR ("Table.Close" / "Table.Open") but this solutions not worked.
Somebody knows if exists some solution for this problem.
Thanks...
Do a double click on the IBTransaction component and choose Snapshot, I think this is the lowest isolation level. I have not network and can not taste it.
I hope it will work successful,
emil
I hope it will work successful,
emil
Emil,
I tried your first suggestion didn't work. But I did try
"Read_Committed" option and worked.
You can explain for me what happening in my application when I choose this option.
Thanks one more time.
-- Elielson
I tried your first suggestion didn't work. But I did try
"Read_Committed" option and worked.
You can explain for me what happening in my application when I choose this option.
Thanks one more time.
-- Elielson
I found this explanation:
ISOLATION LEVEL determines how a transaction interacts with other simultaneous transactions accessing the same tables. The default ISOLATION LEVEL is SNAPSHOT. It provides a repeatable-read view of the database at the moment the transaction starts. Changes made by other simultaneous transactions are not visible.
SNAPSHOT TABLE STABILITY provides a repeatable read of the database by ensuring that transactions cannot write to tables, though they may still be able to read from them.
READ COMMITTED enables a transaction to see the most recently committed changes made by other simultaneous transactions. It can also update rows as long as no update conflict occurs. Uncommitted changes made by other transactions remain invisible until committed.
emil
ISOLATION LEVEL determines how a transaction interacts with other simultaneous transactions accessing the same tables. The default ISOLATION LEVEL is SNAPSHOT. It provides a repeatable-read view of the database at the moment the transaction starts. Changes made by other simultaneous transactions are not visible.
SNAPSHOT TABLE STABILITY provides a repeatable read of the database by ensuring that transactions cannot write to tables, though they may still be able to read from them.
READ COMMITTED enables a transaction to see the most recently committed changes made by other simultaneous transactions. It can also update rows as long as no update conflict occurs. Uncommitted changes made by other transactions remain invisible until committed.
emil
Thanks for using Experts Exchange.
Please provide your email to receive a sample view!
*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.