Ivan,

> the easiest way is to remove all dependencies first,
> e.g. something like
> ALTER PROCEDURE A (X INTEGER) AS BEGIN EXIT; END^

I get weird problems when trying to remove the dependencies.

Following your hint, I wrote a long series of

alter procedure...

statements in the script that creates all the SPs.

FB runs several such statements ok, then suddenly the o.s. raises an
error message and _the FB server is halted_.

IBSERVER caused an invalid page error in module
IBSERVER.EXE in 0137:0048eac6.
Registers:
EAX=00000000 CS=0137 EIP=0048eac6 EFLGS=00010202
EBX=8160f4b8 SS=013f ESP=00d4ea2c EBP=00d4ea50
ECX=00000000 DS=013f ESI=00d4f74a FS=2aa7
EDX=00000008 ES=013f EDI=008b1136 GS=0000
Byte at address CS:EIP:
8b 48 04 8b 55 fc 8d 44 8a fc 89 45 f8 eb 09 8b
stack image:
00480000 0186ffff 000000ff 01879764 018797a0 00d4eab0 00000000
00d40000 00000008 00d4eab0 0048e83c 00874c40 00d4ea68 00d4f74a
0043a4c3 565f4449

After a (I hope) careful study of FB system tables, now I find
convenient to issue a

delete from RDB$DEPENDENCIES where RDB$DEPENDENT_TYPE=5

before all the "drop" statements.

This solution seems to work ok, but if you (or anybody else) are
aware of any danger in doing so, please let me know.

Thank you

Duilio