>>If the table is free, you can still use the same concept, you just have to >handle it manually in code from everywhere that records get added to the >table, and you can't use a dbc's stores procedure.
>
>just a side note -
>you can use the DBC stored procedures provided you have SET DATABASE TO the DBC
>if a DBC is the current database you can call its SPs directly
>
>Arnon

This is true, I should have said you can't specify the stored prcedure in the default value.

This is even advantageous speedwise, because a dbc's prcedures are loaded into memory when the database is open, and so will run faster than a prg.