> Hi
>
> There is a limit (not particularly large) to some variable that

tracks

> table changes, that means that after a certain number off DDL

changes to

> a table the DB needs to be backed up and restored (or sweeped

???).

> Others could give much better detail, but suffice to say making

lots of

> DDl changes to a table is not a good move in FB, you need to look

for

> other ways to achieve what you are wanting. Perhaps creating a
> differently named table for each change would be a relatively

simple

> work around.

The application's purpose is to modify the structure of existing
tables with data that were used for older version of some client
program so that the database would be acceptable for the newer
version of this program. The workaround is not acceptable due to huge
amount of time required for copying the data from the old tables.

Also we have found that in case of reconnecting to server after
described error appears, next DDL commands are executed correctly
(but then, after executing the same count of commands the begin to
fail again). Maybe this variable is stored only during the connect
session.