Combination of SQL Server and Windows -- they perform different tasks.
Prevent the users from seeing your application via Windows, then
control what they are allowed to do via database security.
The roll-your-own solution is not recommended.
On Thu, 14 Apr 2005 09:02:49 -0300, "Retf" <(E-Mail Removed)> wrote:
>Hi,
>
>I need develop a security application, and I would like know what is better
>way to control user access (authentication) in my application.
>
>
>
>Is better:
>
>Control in SQL Server. (SQL Logins)
>
>Control in Windows. (Windows Login)
>
>Control in table of user in my database. (My application control this)
>
>
>
>Thanks.
>
**********************
(E-Mail Removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security