Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 4 of 4 total |
temporary files not cleaned up |
Tue, Oct 9 2007 10:28 AM | Permanent Link |
Daniel Lundin | I discovered that if an exception is raised in a
TTable.OnOptimizeProgress event handler, temporary files created by DBISAM during the optimization process is not removed. I use this event handler to check if the user has cancelled the optimization, and if cancelled I raise an exception. Can this be fixed or has it already been fixed in any newer version (has not been able to find any info about that)? I'm using DBISAM version 4.22 Build 2. TIA Daniel |
Wed, Oct 10 2007 8:36 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Daniel,
<< I discovered that if an exception is raised in a TTable.OnOptimizeProgress event handler, temporary files created by DBISAM during the optimization process is not removed. I use this event handler to check if the user has cancelled the optimization, and if cancelled I raise an exception. Can this be fixed or has it already been fixed in any newer version (has not been able to find any info about that)? I'm using DBISAM version 4.22 Build 2. >> It isn't a good idea to raise an exception in the OnOptimizeProgress event handler. The OptimizeTable method is not intended to be interrupted, which is why there isn't an abort option for that event handler. -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Oct 10 2007 8:48 AM | Permanent Link |
Daniel Lundin | Ok, so there is no way to "cancel" an optimize operation? I guess that
this apply to the RepairTable method also? > > << I discovered that if an exception is raised in a > TTable.OnOptimizeProgress event handler, temporary files created by DBISAM > during the optimization process is not removed. I use this event handler to > check if the user has cancelled the optimization, and if cancelled I raise > an exception. Can this be fixed or has it already been fixed in any newer > version (has not been able to find any info about that)? I'm using DBISAM > version 4.22 Build 2. >> > > It isn't a good idea to raise an exception in the OnOptimizeProgress event > handler. The OptimizeTable method is not intended to be interrupted, which > is why there isn't an abort option for that event handler. > |
Thu, Oct 11 2007 12:52 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Daniel,
<< Ok, so there is no way to "cancel" an optimize operation? I guess that this apply to the RepairTable method also? >> Correct. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Wednesday, April 24, 2024 at 11:07 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |