security with one user name

[Jim]

I'm working on a project that uses a hosted SQL 2000 db.
The hosting provider only only has given me on administrative user account.
Assuming that I only ever have that admin account to link to the db. what
would be the best way to secure specific tables from the users.

I'd like to stay away from ODBC because anybody with the right tool could
open the db.

Currently I'm using an access 2003 project as the front end.
It apears that savy users can get to the database window and get access to
the tables therin.
Is there a way to prevent users from getting to the table information using
a project.
Is the a better way to link to the db that would alow me to specify specific
tables or views then to use the connection wizard.

Thanks Jim

[Larry Linson]

"Jim" wrote

I'm working on a project that uses
a hosted SQL 2000 db.

Hosted on a web server? If so, you can create .asp or ASP.NET pages
with which the user interacts, that do all the access and update --
that's normally the only situation in which I think it would be
appropriate to have just one userid (and even then, you should have at
least one user userid to go along with the admin id). Well, unless you
are like two colleagues of mine, half a continent apart, working in
different industries, who each have applications with one workstation
using a server database.

I can think of no way to have secure access to that server data with
only one userid, and that an admin id. You'd best have a talk with
your host provider.

Larry Linson
Microsoft Access MVP