Hi


I'm just getting started with MadExcept and am wondering what the effect on DBISAM tables will be if a user chooses to close the application from within MadExcept.   Will the application close gracefully or will there be a possibility of corrupt tables?  My application runs in both file server mode and c/s.
I presume that with c/s the tables will be safe but no sure about file server

Cheers

Jeff

Cross posted to DBISAM and MadExcept newsgroups
--
Jeff Cook
Aspect Systems Ltd
Phone: +64-9-424 5388
Skype: jeffcooknz
www.aspect.co.nz

Jeff Cook wrote:
> Hi
>
>
> I'm just getting started with MadExcept and am wondering what the
> effect on DBISAM tables will be if a user chooses to close the
> application from within MadExcept. Will the application close
> gracefully or will there be a possibility of corrupt tables? My
> application runs in both file server mode and c/s. I presume that
> with c/s the tables will be safe but no sure about file server

No changes in behaviour - madExcept does not help the application to crash
cleaner, it just records the last cries.

Ralf

"Ralf Mimoun" <nospam@rad-on.de> wrote on Tue, 7 Feb 2006 01:54:06 +0100

>
>No changes in behaviour - madExcept does not help the application to crash
>cleaner, it just records the last cries.
>

Ralf


Thanks for that.  I was just concerned that madExcept/CloseApplication didn't make anything worse.  We've had a good run out of DBISAM with virtually file corruption and absolutely none that could be blamed squarely on our application, despite bugs and crashes over the years.   I'd hate to introduce the possibility through a "new" bit of software.

Cheers

Jeff

--
Jeff Cook
Aspect Systems Ltd
Phone: +64-9-424 5388
Skype: jeffcooknz
www.aspect.co.nz

I have never seen database corruption when MadExcept is
used to Close an app.  Done it myself more than a few times.

But I guess it all depends...  

There's a question about this on the madExcept newsgroups, and you can
hook it so that you can close your databases nicely if you want.

/Matthew Jones/

Jeff Cook wrote:
....
> I'd hate to introduce the possibility through a "new" bit of
> software.

madExcept is one of the best investments I ever made. The only problem: it
is waaaay too cheap.

Ralf

matthew@matthewdelme-jones.delme.com (Matthew Jones) wrote on Tue, 7 Feb 2006 10:40 +0000 (GMT Standard Time)

>There's a question about this on the madExcept newsgroups, and you can
>hook it so that you can close your databases nicely if you want.
>
>/Matthew Jones/
Matthew

Yes, that was my crosspost probably.  This was Mathias' reply

================================================
This was madExcept's "close application" uses TerminateProcess(me).
So it's a very unpolite termination. Not sure how DBISAM
will behave.

What you can do is to call RegisterExceptActionHandler
to be notified about when the user pressed "close app".
You can then shutdown the tables gratefully. However,
please note that if the process got unstable, trying
to shutdown the tables may result in follow up problems
like program freeze or more exceptions.
================================================


I suspect that it will be best for me to leave well alone, but I might play around with it.

Cheers

Jeff

--
Jeff Cook
Aspect Systems Ltd
Phone: +64-9-424 5388
Skype: jeffcooknz
www.aspect.co.nz

Jeff,

....
> I suspect that it will be best for me to leave well alone, but I
> might play around with it.

I did not touch it - you never know if thinks get worse when you try
something after a crash. madExcept is so great in hunting bugs, after a
whily you simply don't get any crashes (or at least only once a year). Ergo:
no need to handle the db closing thing

Ralf