Sorry

In response to my own question...

The following SQL will list all the dependencies in the ClientCustom table

SELECT DISTINCT dep.RDB$Field_Name AS FieldName
FROM RDB$Dependencies dep
WHERE UPPER(dep.RDB$Depended_On_Name) = 'CLIENTCUSTOM'

Is this safe to use? In my results I get the field I knew was in use by
a stored procedure which is good. However I also get a dependency with
no field name, what does this mean?


Rob Martin
Software Engineer

phone +64 03 377 0495
fax +64 03 377 0496
web www.chreos.com

Wild Software Ltd



Robert martin wrote:

>Hi
>
>We have an issue where clients can add their own custom fields to our
>database (any data type). They can also edit these field types, say
>changing from 10 to 15 chars.
>
>We have a problem where the alteration process causes an error due to a
>stored procedure (and probably a view) that is based on the particular
>field exists. Is there a way to
>
>a) Detect a dependency and not alter the field.
>b) Easily disable a stored procedure and later re-enable.
>
>TIA
>Rob
>
>
>