FH Database ??
Posted: 07 Jun 2018 16:10
Hi
I'm using latest version of FH.
Yesterday, I spent quite a while putting information into FH.
Then, just before I shut down (why is it always just BEFORE), my graphics card & driver went nuts, pushing the machine into a loop from which it just wouldn't recover.
I shut the machine down without the luxury of a soft landing for FH.
Fortunately, when I booted back up, there didn't appear to be too much wrong, except where I had entered files as Media on specific entries.
These files were no longer listed.
So I decided to go through and re-load them in the appropriate entries.
However, whenever I try, FH comes up with the fact it is going to name <filename> as <filename(2)> to avoid confusion with an existing file.
So I though I'd simply re-link with the file, only to discover that they are not listed at all on the media records page.
(Hope that all makes sense).
I wondered if the problem lies in the DB, where there are still names & pointers to files which, because of the crash, are no longer there.
If so, is there a way of checking the DB for accuracy and continuity errors?
At the moment, the problem is irritating rather than dangerous, but I'm left with the uneasy feeling that there might be something else there which I have yet to encounter.
Any views?
I'm using latest version of FH.
Yesterday, I spent quite a while putting information into FH.
Then, just before I shut down (why is it always just BEFORE), my graphics card & driver went nuts, pushing the machine into a loop from which it just wouldn't recover.
I shut the machine down without the luxury of a soft landing for FH.
Fortunately, when I booted back up, there didn't appear to be too much wrong, except where I had entered files as Media on specific entries.
These files were no longer listed.
So I decided to go through and re-load them in the appropriate entries.
However, whenever I try, FH comes up with the fact it is going to name <filename> as <filename(2)> to avoid confusion with an existing file.
So I though I'd simply re-link with the file, only to discover that they are not listed at all on the media records page.
(Hope that all makes sense).
I wondered if the problem lies in the DB, where there are still names & pointers to files which, because of the crash, are no longer there.
If so, is there a way of checking the DB for accuracy and continuity errors?
At the moment, the problem is irritating rather than dangerous, but I'm left with the uneasy feeling that there might be something else there which I have yet to encounter.
Any views?