Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB SQL » View Thread |
Messages 1 to 10 of 13 total |
How to resolve provider errors |
Tue, Aug 11 2009 10:22 PM | Permanent Link |
Jeff Dunlop | When using a ClientDataSet, how do I with Elevate resolve "Record not found or modified by
another user"? When I specify an action of raApply which should force my current change to post through, I just get another Record not found exception. |
Thu, Aug 13 2009 11:23 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Jeff,
<< When using a ClientDataSet, how do I with Elevate resolve "Record not found or modified by another user"? When I specify an action of raApply which should force my current change to post through, I just get another Record not found exception. >> You can't force a change through when such an error occurs. The only way to do so is to turn off (set to False) the TEDBSession.RecordChangeDetection property so that the only exceptions occur are those regarding a situation where a row has been deleted. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Aug 24 2009 3:07 AM | Permanent Link |
Jeff Dunlop | When I set the property to false, on inspection it is still set to true and the update
fails in the same way. I've tried setting it with both opportunistic and pessimistic locking. TEDBSession *session = new TEDBSession(NULL); session->SessionName = "Session_Foo"; session->LoginUser = user; session->LoginPassword = pwd; session->SessionType = stRemote; session->RemoteAddress = addr; session->RecordLockProtocol = lpOptimistic; session->RecordChangeDetection = false; |
Mon, Aug 24 2009 12:53 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Jeff,
<< When I set the property to false, on inspection it is still set to true and the update fails in the same way. I've tried setting it with both opportunistic and pessimistic locking. >> So you're saying that the property assignment to False doesn't change the property to False ? Are you sure about that ? -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Aug 24 2009 6:36 PM | Permanent Link |
Jeff Dunlop | The code as listed when run from a BPL doesn't accept changes to RecordLockProtocol or
RecordChangeDetection. SetPropValue equally does not work. When run from the .exe, it works fine. I don't think it's the debugger playing up because the application behaves like these features are set properly. Any idea at all? C++ Builder 2009. |
Tue, Aug 25 2009 8:05 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Jeff,
<< The code as listed when run from a BPL doesn't accept changes to RecordLockProtocol or RecordChangeDetection. SetPropValue equally does not work. When run from the .exe, it works fine. I don't think it's the debugger playing up because the application behaves like these features are set properly. Any idea at all? C++ Builder 2009. >> Hmm, that would indicate to me that there's a possible mismatch between the runtime .bpl and the .dcp used to compile the application. Did you check and make sure that you've got the correct .bpl ? -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Aug 26 2009 6:03 PM | Permanent Link |
Jeff Dunlop | Wow. No idea how long that previous build elevate .bpl has been sitting in my system32
directory. Nice spot. |
Thu, Aug 27 2009 11:59 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Jeff,
<< Wow. No idea how long that previous build elevate .bpl has been sitting in my system32 directory. Nice spot. >> That was probably our fault. We switched the installations to putting the runtime .bpl in the \Delphi\Lib directory a few months ago, and it might have been left there during the switch over in the installations. -- Tim Young Elevate Software www.elevatesoft.com |
Sun, Aug 30 2009 8:55 PM | Permanent Link |
Jeff Dunlop | Well I'm still getting the same results. The properties are being set as described, but
the same exceptions are being thrown and the provider handlers attempting to resolve the errors aren't having any effect. |
Mon, Aug 31 2009 2:58 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Jeff,
<< Well I'm still getting the same results. The properties are being set as described, but the same exceptions are being thrown and the provider handlers attempting to resolve the errors aren't having any effect. >> Can you send me an example of what you're seeing ? I thought that you were referring to the EDB "record modified" exception, but it appears that the error message is coming from somewhere else. Also, remember that we don't control the CDS/provider code, so I may be limited in what I can do to resolve this issue. -- Tim Young Elevate Software www.elevatesoft.com |
Page 1 of 2 | Next Page » | |
Jump to Page: 1 2 |
This web page was last updated on Sunday, May 19, 2024 at 08:46 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |