🚀 go-pugleaf

We use TSQLConnection.ExecuteDirect('CREATE TABLE')

we have found however that it is irrelevant whether we use the
InterXPress driver or the Delphi Native Interbase DBXPRESS driver.

However I have been able to put my finger on this.
If the database was built by IB6016 the FORMATID is incremented every
time a dependant trigger/Stored procedure/view is created/dropped.
So every time we do a BLR data refresh the FORMATID is being incremented
by up to 15 versions in a IB6016 database.
I would like to retract the statement that none of the FORMATID is over 50.
It is more correct that I have not found a database with the FORMATID over
50.

So If the problem is the "Too many versions" problem without the exception
being generated. Then we can modify the way we change the BLR.( we will do
this anyway)

Regards,

Robert.

"Thomas Steinmaurer" <t.steinmaurer@_no_upscene_spam_.com> wrote in message
news:4173fe08@newsgroups.borland.com...
> > It seems in this case:
> > while the fix is the same backup/restore
> > the problem is not the same.
> >
> > I have been investigating and have found that
> > what Jeff and Bill are talking about is the
> > FORMATID value in the RDB$RELATIONS table.
> >
> > None of these values in any of our systems is over 50.
> > Also no "Too many versions" exception message was generated.
> >
> > All that happenned is that the MetaData was not actually created.
> > after a CREATE TABLE/CREATE PROCEDURE statement.
> >
> > This happened in half of our systems at around the same time.
> >
> > I am still very perplexed.
>
> Do you explicitely COMMIT DDL statements, or do you
> use AUTODDL ON? Perhaps AUTODDL OFF on some
> sites?
>
> What tool are you using to create tables, ...?
>
> Best Regards,
> Thomas Steinmaurer
> LogManager Series - Logging/Auditing Suites supporting
> InterBase, Firebird, Advantage Database and MS SQL Server
> Upscene Productions
> http://www.upscene.com
>
>