>Hi Ed,
>
>Thanks for your comments.
>
>I use to include the output from GENDBC in my projects, because i give the the user the posibility to create empty databases (for example: every year), and assign a new path.
>
>Isn't this a normal practice? or You do it in a different way?
>

Yes, it's normal practice, but not mine. I've been using Stonefield SDT product for a number of years, and it's miles and miles more effective than the GENDBC code, and it handles DBC and table updates via metadata, relible reindexing and packing, simple data table repair, and provides very useful extensions to the .DBC; it's probably the best third party add-on I've purchased. And if you join UT and pay for a PUTM, the discount for PUTM members covers the cost of the PUTM for a year...

>Thanks,
>
>
>Juan Carlos
>
>
>>
>>I'm not sure why you've included the output from GENDBC, but the references are to stored procedures representing the relational triggers stored in the database container. To avoid the errors, you'd need to place EXTERNAL PROCEDURE name of each RI trigger referenced in the affected modules, because the stored procedures are resolved at runtime by calls to the stored procedures, but the compiler is unaware that this is going to happen.