![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Enhancement Requests and Suggestions » View Thread |
Messages 1 to 4 of 4 total |
![]() |
Sat, Dec 27 2008 4:55 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Tim
Can this be altered to a function returning True/False? It would make it much easier to handle flow control rather than having to handle exceptions. Roy Lambert |
Sat, Dec 27 2008 2:28 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Roy,
<< Can this be altered to a function returning True/False? It would make it much easier to handle flow control rather than having to handle exceptions. >> I'll check and see, but probably not (without a lot of changes to the underlying engine code that I'm really loathe to do at this point). The issue is how the unwinding is expected to occur in the engine itself. -- Tim Young Elevate Software www.elevatesoft.com |
Sun, Dec 28 2008 5:00 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Tim
> It would make it much easier to handle flow control rather than having to >handle exceptions. >> > >I'll check and see, but probably not (without a lot of changes to the >underlying engine code that I'm really loathe to do at this point). The >issue is how the unwinding is expected to occur in the engine itself. I was thinking more in terms of just altering the code in edbcomps. I should have known it wouldn't be that easy ![]() Looking at edbcomps I see UnlockCurrentRecord also has an exception handler. What sort of exceptions could this throw? Just being nosey cos I can't visualise what this could be. Roy Lambert |
Mon, Dec 29 2008 3:40 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Roy,
<< I was thinking more in terms of just altering the code in edbcomps. I should have known it wouldn't be that easy ![]() function for my table derivative. Can you tell me what the exception is if it just can't lock it rather than there is a serious problem that needs attention? >> Yep, the identifier is: EDB_ERROR_LOCKROW in the edberror unit. << Looking at edbcomps I see UnlockCurrentRecord also has an exception handler. What sort of exceptions could this throw? Just being nosey cos I can't visualise what this could be. >> The row that you are trying to lock could have been deleted, or with a remote session there could be an issue with the remote call to the ElevateDB Server. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Wednesday, August 14, 2024 at 03:12 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |