Rick

This is the old TURBOGTX problem

The TI transactions log has got out of step with your Image root.

The solution is:
Ensuring that no-one has the file TURBOGTX.PUB.SYS open purge it using
either STORE - PURGE or FSCHECK as it is a priv mode file.

The system will re-build it as soon as it needs it.

The cause is usually that a TIDB has been restored to another group or
account.
Ken Vickers

LINKWAY Development and Support

__________________________________

Computing Solutions Limited

Tel. +44 1905 794400

Fax. +44 1905 794464

mailto:[log in to unmask]

http://www.csllink.com

__________________________________



<[log in to unmask]> wrote in message news:8ve9ee$om3$1@nnrp1.deja.com...
> In article <[log in to unmask]>,
>   "Rick Ingham" <[log in to unmask]> wrote:
> > Can anyone point me to a straight forward example or tutorial for
> providing ODBC updateable access to an Image data base start to
> > finish?
> >
> > --
> > Rick Ingham
> > (RDIngham at Home dot Com)
> >
> >
>
> I'm accessing the DBE as the creator of the data base and the DBE
> environment.  I've done a GRANT ALL to myself.  The message(s) I'm
> getting are these:
>
> isql=> connect to 'flibdbe';
> isql=> delete from flib.flib_xml where xml_id = 'rick';
> IMAGE/SQL error 164; TurboIMAGE error -242; TurboIMAGE intrinsic 420, &
> Auxiliary error 6554488.  (DBERR 13552)
> INSERT/UPDATE/DELETE statement had no effect due to execution errors.
> (DBERR 2292)
> Number of rows processed is 0
>
>
> Rick.
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.