Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 3 of 3 total |
8708's as was |
Tue, Dec 18 2007 8:11 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | I've RTFM but I'd like a bit of clarification please.
In DBISAM with the LockProtocol set to pessimistic if the row had been changed then when we went to edit it we received the good old 8708. Am I correct in assuming that in EDB, with RecordLockProtocol set to pessimistic, and RecordChangeDetection set to false we will no longer receive the error (now 1007/8)? If I am correct is the record data being displayed refreshed prior to editing or what? Roy Lambert |
Tue, Dec 18 2007 3:38 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< Am I correct in assuming that in EDB, with RecordLockProtocol set to pessimistic, and RecordChangeDetection set to false we will no longer receive the error (now 1007/8)? >> Correct. << If I am correct is the record data being displayed refreshed prior to editing or what? >> Yes, the row data is refreshed when the row is edited, so the changes will be there. The only difference is that EDB simply won't say "Hey ! The row changed from what you were just looking at prior to the edit !". -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Dec 19 2007 5:46 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
Goody I can retire my 8708 eaters. Roy Lambert |
This web page was last updated on Monday, April 29, 2024 at 05:23 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |