GREMLINS!!

[MelJ]

I've been sitting here since about 7 this morning working on my solution. Everything is going OK and I'm making descent progress. Suddenly Filemaker starts getting a little slow and suddenly LOCKS UP! (as it often does)

So, as usual, I have to give FileMaker a Hard Close and reboot my computer just as an extra precaution.

When It comes back up, it's like all of my scripts and layouts went through a time warp back to about 10 am this morning. Everything I had done from 10 to 3 WAS GONE!

Does anyone have an idea how this could happen?

Does FileMaker not actually save your work when you think it does?

Thanks,

Mel

[Lee Smith]

Maybe this article can shed some light on the subject for you. Link

Lee

[MelJ]

I need to make an appt. with my shrink after reading that article.

Depression is setting in.

Thanks for the response Lee,

Mel

[Lee Smith]

Any one who has had a file go corrupt, feels your pain.

Lee

[David Jondreau]

Suddenly Filemaker starts getting a little slow and suddenly LOCKS UP! ([color:red]as it often does)

...

So, [color:red]as usual, I have to give FileMaker a Hard Close and reboot my computer just as an extra precaution.

You seem to have accepted something as normal that isn't.

[MelJ]

Thanks for the response Crazy Eye.

When I say "As Usual" means that FileMaker will lock up on me on an average of every month or so.(with average hours spent maybe 40 or so a week) I have a day job so I only get to work on it maybe 4 hours a day then 14 hours Sat & Sun. I post the hours to give you some kind of indication how many hours spent versus the frequency of crashes.

Any Idea what might be happening?

Many Thanks,

Mel

[Fenton]

I would think that once a month was too much. But I suppose it depends on the general health and type of computer.

However, if you're in this situation, there is something you should be doing, what I do when I am working on a serious file. Every time you take a break, and I mean every couple of hours, close the file. Zip it, after throwing the earlier zipped version in the trash.* Open the file again. You have now "safely saved" the work you did. It only takes seconds (depends on size of file and speed of computer).

*Every once in a while you might want to save the earlier zipped version, say between major overhauls, when importing data from a client, etc.. But, it is the frequency of saved zips which matters, not the accumulation of obsolete code. I'm cautious, but not anal retentive :-]

[Anuviel]

What I usually do, might not be conventional but every 3 hours or whatever time frequency I set depending on the project and how much I get done, I close the file, exit FM, navigate to where I saved the file, duplicate it, rename the copy to .FMbak and put it into Archive folder.

Have not run into problems yet (that is not to say that I will not...)