Subject | Re: [ib-support] Crashing of Interbase |
---|---|
Author | Rohit Gupta |
Post date | 2001-09-05T02:58:47Z |
From: "Claudio Valderrama C." <cvalde@...>
Date sent: Tue, 4 Sep 2001 02:52:57 -0400
Send reply to: ib-support@yahoogroups.com
Subject: Re: [ib-support] Crashing of Interbase
&
Firebird WI-TI.0.0.338
consist of
Insert Record in Table1
Insert Record in Table2
Lock Record in Table1 (created above)
Cancel Edit on the Record
Lock Record in Table1 (created above) and Table2 (created above)
Cancel Edit on both Records
Open New form with Table1 for browsing ----> Death
There is nothing complicated in the SQLs. The only minor
complication is to lock the record prior to editing (using transaction)
Regards
Rohit
======================================================================
CFL - Computer Fanatics Ltd. 21 Barry's Point Road, AKL, New Zealand
PH (649) 489-2280
FX (649) 489-2290
email rohit@... or r.gupta@...
======================================================================
Date sent: Tue, 4 Sep 2001 02:52:57 -0400
Send reply to: ib-support@yahoogroups.com
Subject: Re: [ib-support] Crashing of Interbase
> ""Rohit Gupta"" <rohit@...> wrote in messageInterBase 6 - WI-V6.0.0.0627
> news:3B95122A.21484.43CA1D96@localhost...
> >
> > Does anyone know what this means ? It is very repeatable.
> >
> > RG (Client) Tue Sep 04 17:34:51 2001
> >
> > e:\program files\borland\intrbase\bin\ibserver.exe: terminated
> > abnormally (-1073741819)
> > Regards
>
> It means the server died due to an internal failure.
> If you say it's very repeatable, then provide at least:
> - Server version.
&
Firebird WI-TI.0.0.338
> - Type of connection (local, TCP, etc.)Local
> - What kind of statement you suspect may cause the problem. Do you have someIts in an app - repeatable by doing the same operations which
> complex SELECT statements? Do you know if one of your procedures causes the
> failure? Can you try to isolate the problem? If you can isolate it, can you
> try the same on FB?
consist of
Insert Record in Table1
Insert Record in Table2
Lock Record in Table1 (created above)
Cancel Edit on the Record
Lock Record in Table1 (created above) and Table2 (created above)
Cancel Edit on both Records
Open New form with Table1 for browsing ----> Death
There is nothing complicated in the SQLs. The only minor
complication is to lock the record prior to editing (using transaction)
Regards
Rohit
======================================================================
CFL - Computer Fanatics Ltd. 21 Barry's Point Road, AKL, New Zealand
PH (649) 489-2280
FX (649) 489-2290
email rohit@... or r.gupta@...
======================================================================