Hi,

I have an SQL Server 2000 database which I am going to install on a
Windows 2000/XP Workstation under SQL Server 2000 Personal Edition on
a client pc. There will be no other SQL databases on this pc and I
will the the only one using SQL.

This PC will be networked. The network administrator will have full
access to this PC but I have full control of over how SQL is setup.

I have an Excel based front-end (created by me) that will be used to
access this DB. This should
be the only way the user can access this database. There will be only
one user.

I don't want users to b able to view my procedures and also tables
using QA or Enterprise Manager.

What is the based and the simplest way to acheive this?

Thanks.

Actually, I have 5 to 10 procedures - which are critical - I can just
encrypt them. I guess, I can easily easily replace them with a new
procedure, if there is any code change or correction, right?

Alternatively,
Can I install SQL with only one SQL User (no windows account access).
And hard code this user in my front-end application. I will be the
only one who would know this username and password. Will this work???

Note that this will be a single user DB - no other DBs in this SQL
installation.

You have several things going on here.
If you want people to only be able use your Excel front end application, you
should use Application Roles. The password will only be as secure as your
Excel security, so that might not be best.
A better (or perhaps redundant) solution, is to keep the Business Rules on
SQL Server, so even if someone executes the stored procedure from Query
Analyzer, it will still behave correctly.
Last, if you don't control the client computer, you don't really control the
database. For instance an administrator on the client, could stop SQL
Server, copy the mdf file to another computer and attach the database to an
instance of SQL Server on which they have sysadmin permissions. Then they
own the database and can see the procedures.
Lastly, you can create the procedures using the WITH ENCRYPTION option, to
make it harder for people to see what's going on in the proc. That does not
offer complete security but can be part of defense in depth, and keep out
the curious.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Jay" <jay6447@hotmail.com> wrote in message
news:9a55bf8e-b69c-4493-a026-77c2d7f08c45@j33g2000pri.googlegroups.com...
> Actually, I have 5 to 10 procedures - which are critical - I can just
> encrypt them. I guess, I can easily easily replace them with a new
> procedure, if there is any code change or correction, right?
>
> Alternatively,
> Can I install SQL with only one SQL User (no windows account access).
> And hard code this user in my front-end application. I will be the
> only one who would know this username and password. Will this work???
>
> Note that this will be a single user DB - no other DBs in this SQL
> installation.