>You told us that you did that. If the user does not have SELECT permission >on a table, they will not be able to view the data within the table. They >will be able to see the table names because Public has SELECT on the system >tables.

>If you don't want anyone to have any access, create a login that is only >used by your application.

That is what I've done, but like you said, PUBLIC has access to SELECT on systems's table. That is what I want to revoke. Any ways ???


>The downside is that you're not letting your customer get to their data >using any number of tools, such as Analysis Services 2000, to extend the >value of your application.

I've create another user that has SELECT on views that are a logical representation of my physical model. You are right, it extends the value of the application, but user do not have to be aware of the physical implementation of solutions. They need the data, not the system's internal.


>Compile your scripts into an .EXE. Let the EXE build your database.
OK, don't know how to do that, i'll read first :-)


Thanks again for you appreciated help!
HAND!



-Mike