Abnormal Quit Issues

[jda]

>We've been experiencing a fair amount of data loss when we quit our 
>application abnormally.  Normally I wouldn't be concerned too much 
>about it since we're in development phase and all sorts of bad 
>things happen.
>
>However, yesterday, one of the beta testers opened a screen up that 
>simply viewed some records.  He hadn't added any new data, deleted 
>anything and then simply force-quit the application to see what 
>would happen.  I've verified that there is no record locking going 
>on when viewing the data.  He then opened the database again and 
>could visibly see some data not there.
>
>What can we do to minimize this risk?  Has anyone else see this behavior?
>
>RB 2005 using 2.05fc5 on Tiger.
>

I have found more than once that when I abort in the RB debugger the 
db is trashed, event though it was not in the middle of a read/write. 
In fact, I have one that was trashed in this way that actually 
reported as OK with diagnose, but crashes my app when I try to open 
it (no log).

Jon