No ideas, but I can't see how a client can be doing this by corrupting it's
own memory structures. The whole point of the level of abstraction SQL
based servers are supposed to give is that a rogue client can not corrupt
the db.

When you say you can reproduce, you mean you can take a perfectly good db
and trash it by running your apps?

What about the old chestnut of the connection string error? (server:e:\data
vs server: e :\data)?

Cheers,

JAC.

""Wilson, Fred"" <fred.wilson@...> wrote in message
news:E9E4431A916AD21191FD00104B986AEFC238C1@......

> IB5.6 running on W2000 (and NT4.0).
> Client applications using the IB API directly. We obviously done (or am
> doing) something wrong. We can reproduce the error(s) below with some

work.

> I suspect that the client application(s) is trashing some memory somewhere
> (maybe the DPB, the TPB, XSQLDA, etc).. Any ideas what, specifically, can
> cause the below, from the Interbase Log:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> BUBBA (Server) Mon Apr 01 11:29:04 2002
> Database: D:\INTRBASE\BIN\GA
> internal gds software consistency check (pointer page vanished from
> DPM_next (249))
>
>
> BUBBA (Server) Mon Apr 01 11:42:19 2002
> Database: D:\INTRBASE\BIN\GA
> internal gds software consistency check (pointer page vanished from
> DPM_next (249))
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Thanks,
>
> Best,
> Fred Wilson
> SE, Bell & Howell
> fred.wilson@...
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>