>Is there a way to stop acess to my DBC ?
>I have some Stored procedure i want to hide to users.
>I have set up a password when an user try to open a table, but if i open the DBC like a table (USe Data.DBC) i can see all the info written in it.

Like Doug said, encrypting your DBC with something like Cryptor (a commercial product) may be the best solution.

In my case, I try to avoid using DBC stored procedures because they are not reusable or portable and they usually have strong coupling to the DBC and the app. Besides that, they are not protected, as per your concern.

One way around that, is to move them out of the DBC, and put them in separate programs (maybe in a DLL) or even in a table in a memo field, where you could use strong encryption measures.

You would have to consider ease of access, speed of execution, ease of maintenance and security in these cases, to see which option works best for you.