Abaksoft Posted May 23, 2017 Share Posted May 23, 2017 Hello Friends, CachedUpdate and Autocommit are two properties very important ! With unigui, we are talking about a hundred users connected at the same time. In such multi users environement, if your CachedUpdate is False (as by Default with IBDAC /Devart), any changes by others users, on a UniDBGrid will attack directly your physical DataBase ! And if you are on this record (80% by chance), you will get this error : Conflict Record. Solution : Make sure : __________________ Autocommit := False; CachedUpdate := True; __________________ it tooks me 4 hours to track the pb ! Regards Quote Link to comment Share on other sites More sharing options...
rencarnacion Posted May 23, 2017 Share Posted May 23, 2017 Excellent, Thanks Quote Link to comment Share on other sites More sharing options...
Administrators Farshad Mohajeri Posted May 23, 2017 Administrators Share Posted May 23, 2017 Thanks for pointing this out. Actually this problem is available for all multi-user client-server database applications. Quote Link to comment Share on other sites More sharing options...
itognet Posted May 23, 2017 Share Posted May 23, 2017 will attack directly your physical DataBase Quote Link to comment Share on other sites More sharing options...
eduardosuruagy Posted May 23, 2017 Share Posted May 23, 2017 I'm using ADO, do you have any settings I need to make in it? Quote Link to comment Share on other sites More sharing options...
rencarnacion Posted May 23, 2017 Share Posted May 23, 2017 ADO can't use cachedupdate Eduardo You won't have these problem Quote Link to comment Share on other sites More sharing options...
eduardosuruagy Posted May 23, 2017 Share Posted May 23, 2017 Ok Quote Link to comment Share on other sites More sharing options...
IRWANTO82 Posted May 26, 2017 Share Posted May 26, 2017 Hello Friends, CachedUpdate and Autocommit are two properties very important ! With unigui, we are talking about a hundred users connected at the same time. In such multi users environement, if your CachedUpdate is False (as by Default with IBDAC /Devart), any changes by others users, on a UniDBGrid will attack directly your physical DataBase ! And if you are on this record (80% by chance), you will get this error : Conflict Record. Solution : Make sure : __________________ Autocommit := False; CachedUpdate := True; __________________ it tooks me 4 hours to track the pb ! Regards how you handle the row for edit? use form for edit row if its important data, and always use lastupdate field to compare data change by other user before post `lastupdate` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.