On Tuesday, July 31, 2001, at 11:20 AM, Joerg Pressel wrote:
> Hi John,
>
>> I had a similar thing "happen" to me. Everything else could open my
>> database
>> except the program that I wrote which constructed it. I finally chased
>> the
>> problem down to a slight change in the db structure (didn't
>> remember). I
>> used VAPP to compare the db structure to what was coded in my program.
>> You
>> might check it. I hope all goes well.
>
> I did not change the db structure - I think Valentina should not crash
> even
> if there is a problem with the structure or the file is corrupted.
>
> Problem is that my app remembers what databases were open and try to
> reopen
> them at next start. Now if a user experiences a crash with the app, the
> db
> gets corrupted and everytime the app is launched, it crashes again,
> because
> it tries to re-open the db. Only workaround for the user is to delete
> the
> prefs. That's bad, because some unexperienced may think the app itself
> is
> crap (well, if it crashes at first it is mostly my fault) and leave it
> alone
> / don't license it.
>
I've crashed RB, oh, hundreds of times with the db open. I've never
gotten a corrupt data file as a result. If you're using a one-file
solution, you might consider using option 5, files + index file. It may
be that the index file is becoming corrupted, and you can safely delete
it on startup if your app realizes that it crashed. Otherwise, this is
mysterious.
Charles Yeomans
©2001 Charles Yeomans |
