HI all,
I know there a lot of threads regarding the packing of tables but my searches brought up very little about packing sets. I know that when packing a set you are actually packing each table within the set....but I recently had something strange happen and am wondering why.
I have had quite a bit of problems with corruption and such, most likely due to a faulty motherboard(which will be replaced soon!). So I have regularly used packing and compacting to help keep things running smoothly.
What happened is that after packing a set(3 tier..parent==child--grandchild) successfully I, for some reason, tried packing just the grandchild and it would not--error came up stating that the .ddd and .ddm files could not have their indices updated. I then tried the set packing and it completed successfully again. But all attempts at packing the single table failed.
So if packing is supposed to update the indices of each table why did the set packing complete with no errors?? Is it possible that the set packing does not always update the indices? Or perhaps the error trap does not always work with sets?
And, of course, I have no way now of replicating this situation as the problem has been fixed.
-------------------------------------------------------------------------
As a side note for whoever may find it useful this is what I tried from various messageboard suggestions on how to get the files packed and then what I actually had to do.
Tried: Deleting all temporary files($...)
Dropping the affected table and then readding it
Restore from a backup(went back to weeks earlier!)
None of the above worked for me this time. What I eventually did which did work was to manually copy the tables files from a recent zip file I had created a couple of days before and then paste them into my current database files. I would have thought that the backups would have fixed it(usually does!) but not this time. Am thinking I may just create a weekly zip file now as a "just in case" type backup now after this happened.
Mike
I know there a lot of threads regarding the packing of tables but my searches brought up very little about packing sets. I know that when packing a set you are actually packing each table within the set....but I recently had something strange happen and am wondering why.
I have had quite a bit of problems with corruption and such, most likely due to a faulty motherboard(which will be replaced soon!). So I have regularly used packing and compacting to help keep things running smoothly.
What happened is that after packing a set(3 tier..parent==child--grandchild) successfully I, for some reason, tried packing just the grandchild and it would not--error came up stating that the .ddd and .ddm files could not have their indices updated. I then tried the set packing and it completed successfully again. But all attempts at packing the single table failed.
So if packing is supposed to update the indices of each table why did the set packing complete with no errors?? Is it possible that the set packing does not always update the indices? Or perhaps the error trap does not always work with sets?
And, of course, I have no way now of replicating this situation as the problem has been fixed.
-------------------------------------------------------------------------
As a side note for whoever may find it useful this is what I tried from various messageboard suggestions on how to get the files packed and then what I actually had to do.
Tried: Deleting all temporary files($...)
Dropping the affected table and then readding it
Restore from a backup(went back to weeks earlier!)
None of the above worked for me this time. What I eventually did which did work was to manually copy the tables files from a recent zip file I had created a couple of days before and then paste them into my current database files. I would have thought that the backups would have fixed it(usually does!) but not this time. Am thinking I may just create a weekly zip file now as a "just in case" type backup now after this happened.
Mike
Comment