I prefer to manage it myself. Users logon to my applications. From there I know who they are and to which options they should have access. From there I enable/disable menu options, fields, buttons, ... from menus or forms.

You could also create database roles into SQL Server.

I prefer to do it this way because you often have cases where a clerck should be given more privileges for a specific task. By using roles, you are suck!


>Thanks Eric and Gorden your suggestions does solve the application Updates problem. however still looking for solution of another Q in same thread.
>The application is using a single database, and about my query for database users, how should i create the secure application(creating database users and privilages and so handling the DSN)
>for ex in SQL SERVER suppose for accounts application we create one login lets say accounts and some password. now when we create DSN or database connection we supply the same to server. and privilages we handle in Application (show/hide programs/menus)
>so my Q is will database user be same for all 100 users and if want to make 4 groups having different access levels; should i manage in application itself....i hope you r getting me...
>means thru application the clerk is having access to one prgram(insert/ update on one table only) but actually the database user(accounts) application is using has access to everything. i mean is it advisable to continue such practise
>whats the best way..the best practise to handle this???