QuinTech Posted November 11, 2004 Posted November 11, 2004 First, a complaint: Why, when i search for "corrupt and must be recovered" on FMI's knowledge base, should i get pages and pages of results that have nothing to do with anything? I know it's been said before, but AAARRRRRRGGGGGHHHHHHH!! Now, my question: I am trying to write up a manual and am looking for the exact wording of the message i will paraphrase here: "[FILENAME] is corrupt and must be recovered. Please select Recover from the File menu." (FMP 6) If anybody has that handy, please post it, for i will soon be forced to open my valuable .fp5 files and then kill the power in the hopes that will corrupt something. TIA, Jerry
Lee Smith Posted November 11, 2004 Posted November 11, 2004 Sorry Jerry, I'm not going to ruin any of my files to verify this, but in the Error codes it shows this: 805 File is damaged; use Recover command HTH Lee
SteveB Posted November 11, 2004 Posted November 11, 2004 "Filename.FP5 is damaged and cannot be opened. Use the Recover command to recover this file." (I always keep a bad file or two around for testing puposes in a separate folder). Steve
Lee Smith Posted November 11, 2004 Posted November 11, 2004 Hi Steve, (I always keep a bad file or two around for testing puposes in a separate folder). What's the name of the folder, Time-Out. Lee
QuinTech Posted November 18, 2004 Author Posted November 18, 2004 Still on this subject... Steve, i read a post of yours from a long time ago about trapping for 805 errors. Were you ever able to figure out a way of doing that? I've read in another post about an idea of using a global field in each file to which "1" or some other flag is written upon a proper shutdown. Then a test for IsEmpty ( relationshgip::flagField ) will show whether or not the file is corrupt. I have enough files that i do not look forward to the propsect of creating relationships to each of them from my opener file for this purpose, and i hope there's another way. TIA, Jerry
SteveB Posted November 20, 2004 Posted November 20, 2004 Jerry, FM ignores the error code when the file is corrupt and puts up its standard error message (as I remember it). I could never trap it, and gave up. But I would sure like to be able to prevent the message from showing up. Steve
Recommended Posts
This topic is 7572 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now