Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 2 of 2 total |
Trapping underlying exception in AlterTable |
Wed, Apr 7 2010 9:07 AM | Permanent Link |
jon bondy | I know that the software we are using is old, but the thought of upgrading terrifies us.
I hope this is a simple question. While doing an AlterTable, the introduction of a new Index caused a duplicate record to occur in the new Index. This in turn caused a run-time exception. The problem is that AlterTable seems to attempt to handle that exception, so that we never hear about the exception in an external TRY/EXCEPT statement. What we see, instead, is a "corrupt header" error, which is better than nothing, but misleading. Do you have any suggestions about ways that we could "see" the original exception more clearly? Thank you! Jon |
Thu, Apr 8 2010 6:43 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Jon,
<< While doing an AlterTable, the introduction of a new Index caused a duplicate record to occur in the new Index. This in turn caused a run-time exception. The problem is that AlterTable seems to attempt to handle that exception, so that we never hear about the exception in an external TRY/EXCEPT statement. What we see, instead, is a "corrupt header" error, which is better than nothing, but misleading. >> This is definitely an old issue and has been fixed. You should consider updating to the latest version - there really isn't any downside to it, if you're coming from an existing 4.x version. Tim Young Elevate Software www.elevatesoft.com |
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 |