Since you can have crossed dependencies,
like procedure A calling procedure B, and
procedure B calling procedure A at the same time,
the easiest way is to remove all dependencies first,
e.g. something like
ALTER PROCEDURE A (X INTEGER) AS BEGIN EXIT; END^
ALTER PROCEDURE B (X INTEGER) AS BEGIN EXIT; END^

DROP PROCEDURE A;
DROP PROCEDURE B;

Ivan


From: "duilio_fos" <irel_llc@...>

> you have an ISQL statement that begins with a long series of
>
> drop procedure...
>
> statements and continues with a long series of
>
> create procedure ...
>
> statements.
>
> Is there any tool that will read the script and return
>
> - a possible order for the "drop procedure..." statements and
> - a possible order for the "create procedure..." statements
>
> so that no dependence error will be given when running the script ?
>
> When the script is complex enough, I find myself spending a long time
> fixing these errors...