"Thierry Holtzmann" <tholtzmann@...> wrote in message
news:3C8F74F5.5040509@......

> What i mean is
> changing say AVALUE COMPUTED BY (AFIELD + 1) into
> AVALUE COMPUTED BY (AFIELD + 2)
> without having to drop and recreate the column because I have also to
> drop related procedures before dropping the column

If the column is referenced in other objects, you're out of luck, at least
trying to do things in the legal way.
For the engine, a change is a change. It's really tricky internally to be
sure the new field preserves the type and size of the old field. Hence, the
engine stops those operations. You could update the field's source
definition and then the field's binary (BLR) definition directly and it
*may* work (in the worst case for you, the engine detects that low level
change, too).

C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing