On 06/03/2011 05:06 AM, munster77054 wrote:

>> Why don't you run your programs in the debugger
>> and find out which statement(s) trigger the crash?
>> Because it concerns multiple programs, the component
>> set may well be the culprit. And if it's the Firebird
>> engine after all, we all would like to know about it,
>> so it can be fixed. But please remember that many of
>> us have been using Fb 2.5 in all kinds of environments
>> without major problems.
> There is no consistency... sometimes at startup; sometimes when processing something, sometimes when using the IBSQL component, sometimes when using native components. As I said before, no problems with 2.1, just 2.5.

Jumping in late to this thread, but I don't think that I see that you
established that it is 2.5 causing you the problem.

What else are you using to access FB has this been updated to 2.5
compatible version?

I can understand your "ghost" process but at this point I think you
should have a test system on which you install your 2.1 software and
then upgrade to 2.5 and test until you see the failure, report the
failure with as much detail as possible here and apply suggested fixes
until you get to a stable version of your software with FB 2.5 at this
point you can go back to your "ghost" system upgrade process - i.e.
don't waste your time with ghosting spend it instead of trying to
isolate your problem.

> I'm in the middle of restoring my system from the WINZIP files, after going through the last three ghost steps to remove, then add 2.1 back. Remember, that I had to go back 4 steps, and then rebuild my computer from there to completion, to insure that the ghosts are pristine.
>
> I've had several friends recommend that I update the programs to use ODBC and use either M$ Access, or MySQL.

Can't speak for MySQL but should you go to MsAccess I am pretty sure you
wouldn't call your friends "friends" that much longer;-) .

Werner