silent abort during "analysing results"
Posted: Thu Aug 18, 2005 3:03 pm
Recently I've been seeing the following behavior with V2.2.
During a file deletion operation (which by the way seems REALLY SLOW in both its phases with a database of any size) there are two phases (as far as the user sees) -- 1. deleting and 2. analysing database (presumbably includes deleting records from the database that contain the deleted files). During the 2nd phase (analysing) IC appears to silently abort. The program just goes away with no messages.
When I re-open IC I find that the files were indeed deleted, but that the records are still in the database. So all of the records have "File not found" messages in one of the thumbnail boxes. So then if I'm still working on that database and I don't want the clutter of those records I have to go back and re-select all of those entries and delete those records which as I've noted in another defect report is an arduously slow process on a database of any size.
So it would be great to figure out why IC is silently aborting during the analysis phase of the delete and fix it. Additionally it might be nice to add a means of automatically selecting all records that contain "File not found" entries or better yet an operation to delete such records. I guess there are other reasons a file in a database might go away and the records really aren't of any use after that (at least to my mind).
-- Tom.
During a file deletion operation (which by the way seems REALLY SLOW in both its phases with a database of any size) there are two phases (as far as the user sees) -- 1. deleting and 2. analysing database (presumbably includes deleting records from the database that contain the deleted files). During the 2nd phase (analysing) IC appears to silently abort. The program just goes away with no messages.
When I re-open IC I find that the files were indeed deleted, but that the records are still in the database. So all of the records have "File not found" messages in one of the thumbnail boxes. So then if I'm still working on that database and I don't want the clutter of those records I have to go back and re-select all of those entries and delete those records which as I've noted in another defect report is an arduously slow process on a database of any size.
So it would be great to figure out why IC is silently aborting during the analysis phase of the delete and fix it. Additionally it might be nice to add a means of automatically selecting all records that contain "File not found" entries or better yet an operation to delete such records. I guess there are other reasons a file in a database might go away and the records really aren't of any use after that (at least to my mind).
-- Tom.