application crashing, need to Recover

[NHuser]

I've been using Filemaker for 15 years and currently have 5.0 Windows version. I use a Dell PC with a Pentium III processor and 256MB of RAM. I daily use about 10 different relational databases and one is 100MB in size. I continuously use my Filemaker databases for 8 to 10 hours every day.

Recently, especially in the 100MB database, but also in a couple of my smaller databases, I have had to Recover them (3 times in the last 2 weeks for the 100MB database, and once each for 3 of my smaller ones). This had almost never happened in the past (except maybe 2 or 3 times in the last 10 years). Just prior to having to Recover them (and it always shows no records or data skipped or lost after the Recover is completed), I had gotten an error window that said something like "you have made an error in the Filemaker application, all previously unsaved data will be lost" and it gives a grayed "close" button as well as a grayed "ignore?" button. It doesn't allow a the "ignore" option, and after I choose "close" it quits the Filemaker application . This has been happening every couple of days for the last couple of weeks. Then, when I go to reopen the database it tells me I need to Recover it, which I do and it works fine until I get the same crashing error window 2 or 3 times again (over the course of a week or so)

Does anybody know what the problem might be? Suggestions? Is there a chance that one day my database will be unrecoverable and I'll lose 15 years of data?

I'd appreciate any help or suggestions anyone can give if you've had similar problems and (hopefully) solutions. Thanks.

[dbhill]

First you need a clone of your undamaged database. Next you should import all records into the clone from the recovered file. You should not use a recovered file in production. Recovery will attempt to preserve your data intact, but it may not recover damaged structure.

It is good design to keep a set of clones of your solution for just such an occasion.

~Dennis

[NHuser]

Thanks Dennis, I appreciate your help.

I wasn't quite sure that a clone would solve the problem, because I didn't know if cloning a database removed all damage that existed in the original database (i.e. if the original had corrupted layouts etc.)

Thanks again.

[Steven H. Blackwell]

quote:

---

Originally posted by NHuser:

Thanks Dennis, I appreciate your help.

I wasn't quite sure that a clone would solve the problem, because I didn't know if cloning a database removed all damage that existed in the original database (i.e. if the original had corrupted layouts etc.)

Thanks again.

---

The act of cloning per se does not eliminate corruption in the structure of the database. You needed to have a clean clone from the outset. It is into a copy of that clone that you import the data from the recovered file.

There is a widespread belief that cloning removes some type of data corruption. I know of no evidence supporting this. There are applications and plug-ins to deal with corrupt data.

HTH

Old Advance Man

[Anatoli]

Maybe there is also the Dell-soundcard problem.

If you have Sound Card on motherboard, try to disable that as well.

It is long shot, but one never knows.

[NHuser]

Hey Old Advance Man,

what applications and/or plugs ins would you recommend to eliminate corrupt data and clean the databases?

NHuser

[Steven H. Blackwell]

quote:

---

Originally posted by Anatoli:

Maybe there is also the Dell-soundcard problem.

If you have Sound Card on motherboard, try to disable that as well.

It is long shot, but one never knows.

---

Take a look at the 5.5v2 updater. I believe it has addressed this issue.

Old Advance Man

[Steven H. Blackwell]

quote:

---

Originally posted by NHuser:

Hey Old Advance Man,

what applications and/or plugs ins would you recommend to eliminate corrupt data and clean the databases?

NHuser

---

David McKee's Character Sieve and BBEdit are good choices. I don't have McKee's URL handy but I'll try to get it and post it.

Old Advance Man