Hi:

Not clear to me what the problem is.  If there is a front end to this
application, don't install it on the "guest" computer.  If there is a
program.exe file that lives on the server, create a security group that has
access to that file, put your regular users in that group, but not the
"guest" user.  Then remove all other security access to that file/folder,
leaving only the security group.

Do not do this with individuals, as it gets too messy to control.  Every
time you add or subtract a user from your network, or promote a new employee
to a "regular user" all you have to do is add them (or remove them) from the
security group.

--
Larry

In article <11a1be10-b2cc-4337-bb8b-40c7c56ffda0@
34g2000hsh.googlegroups.com>, jhunter@huntercomputerinc.com says...

Surely this all depends on how the user gets access to the SQL Server
database.

Many apps use Windows Authentication, and some don't, while others
provide both (either or) - in which case you could change away from WA
to using SQL Server authentication, and given that user doesn't exist in
SQL Server, they won't be able to start the app.

Another way, just remove the front-end SQL Server app from the
workstation.