On Oct 22, 2009, at 9:45 AM, Lorne & Joan Walton wrote:
> As usual, I'm not making myself clear. What I've never seen before
> is "FileMaker unexpectedly quit" after waking from sleep. Repeatedly.
That just tells me that you've never used your files from a host
(server or P2P), because it happens all the time then. But in those
cases the file does not get corrupted. Perhaps some data loss, but no
file corruption. If you are running them single-user, though, a crash
could seriously hose a file and you might not even know it for months.
I maintain a zero-crash policy with my developing and encourage my
clients to do the same.
Wish I could knock a few heads, though, when I open a client's copy of
something and it says, "File was not shut down properly..."
You can lead them to water...
>
> On Oct 22, 2009, at 6:07 AM, Jonathan Fletcher wrote:
>
>> Lorne didn't say that he used the Recover command, but the advice
>> is the same: NEVER use a crashed file. The chance of minor damage
>> rearing its ugly head down the road is too great, and there is no
>> solution but a rebuild at that point. It's safer to NEVER use a
>> crashed file. BTW, an unexpected quit is a crashed file.
>
> That latter point is part of what I was seeking. But what if I don't
> know which file(s) were open when the unexpected quit (crash)
> occurred? Of course, I could go to File:Open Recent and replace the
> top 4 or 5...
Whatever it takes.
>
>> That does not mean that corruption caused the unexpected quits. I
>> would chalk that up to the fact that the OS couldn't manage to
>> restart the file upon waking up. Like I said, my particular brand
>> of common sense (which--alas, all too often--may be different from
>> the next person's common sense) says to never let a FileMaker file
>> be open when you put your computer to sleep.
>
> That's just depressing!
Not for me. I never allow a machine running FMP to go to sleep anyway.
The only time my production machine goes to sleep is when I throw it
into its bag to leave the office. I shut down most of the running
programs then, STARTING with any open FileMaker files. Maybe I've
always been superstitious, but it just FEELS like a bad idea to sleep
an open FMP file.
Another thing I do is try to develop exclusively from a served file.
If you're a TechNet member you can get a copy of Server Advanced for
FREE. That, and the price of a G5 and above and you've got your auto-
backing up, crash-tolerant, production server. Set it to save a few
weeks worth of hourly backups and you're covered for everything except
the building burning down. (And that's an easy one to cover for, as
well, with one of the many $5 a month off-site services.)
> --
> It is a mistake to think you can solve any major problems just with
> potatoes. [Douglas Adams]
Not THAT'S depressing!
j.
--
Jonathan Fletcher
FileMaker 9 & 10 Certified Developer
****NEW Ph no: 502-509-7137****
Project Foreman
NewMedia Construction Co.
[hidden email]
Instigator
The BB&J Network
The "Go-To Guys" for
FileMaker Development in Louisville
www.thebbandj.net
FileMaker Louisville Blog:
http://filemakerlouisville.posterous.com_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
