Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Client/Server » View Thread |
Messages 1 to 2 of 2 total |
Exception Handling in DBISAM 3.30 For Code 11276 |
Fri, May 5 2006 6:19 AM | Permanent Link |
Francois Steyn | Hello
How do you use exception handling in DBISAM 3.30 when the network connection gets dropped or times out? Is it possible to tell the application to reconnect to the database and continue or do you have to terminate the application? The problem is that the user can be busy processing the transaction or just browse the data through a grid. Is it possible to resume a session and just continue processing or do you have to restart the entire session and start processing from scratch? I was thinking of using Application.OnException to determine when the exception occurs, but what do I do then? At that point it can be anywhere in the entire system. Thanks! Francois |
Fri, May 5 2006 2:49 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Francois,
<< How do you use exception handling in DBISAM 3.30 when the network connection gets dropped or times out? Is it possible to tell the application to reconnect to the database and continue or do you have to terminate the application? >> You have to deactivate the session and reactivate it if the connection never recovers. This is something that was improved quite a bit in V4 via an OnRemoteReconnect event handler. << The problem is that the user can be busy processing the transaction or just browse the data through a grid. Is it possible to resume a session and just continue processing or do you have to restart the entire session and start processing from scratch? >> Again, if the connection is gone forever, then you have to restart the session. << I was thinking of using Application.OnException to determine when the exception occurs, but what do I do then? At that point it can be anywhere in the entire system. >> It really doesn't matter at that point, just ignore the exception and try to shutdown the session. You will get a bunch of exceptions during the shutdown of the session, so don't try to shutdown the session multiple times. IOW, set a flag to indicate that you already have started the session shutdown. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Friday, April 19, 2024 at 07:09 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |