>Hi all - I could use some expert advice regarding the (new to me) DBC concept.
>
>My application (FPW2.6) is set up with 22 tables, each in a subdirectory of the application directory on our file server. This way, I can assign "write" access to selected individuals for different tables, and for the rest, the "ADD/EDIT/SAVE/CANCEL/DELETE" buttons are disabled if table is readonly.
>
>How does the use of a DBC affect this approach? Let me say from the start that I really do not want to add passwords and logins to the application if I can avoid it (we spend half our lives logging in LOL).
>
>I like the features offered by the DBC...long field names, min values, etc. But can I still store the individual tables that are contained by the DBC in individual subdirectories? And if so, is the DBC stored in the app directory? Do users need to have anything but readonly access to the DBC?
>
>::scratching head and hopin for help::

What the others told you is true, but I wonder if I understand your intentions correctly- do you wish to have multiple copies of the same table live in different directories so you can assign rights to the table throught the network according to user?

If I understand you, then you cannot do this, because tables store a reference to their containers and containers store paths to their tables. So 2 tables named 'customer' cannot share the same dbc.

Forgive me if I am way off from what you were asking...