>>I have a desktop application (VFP9) which runs in a Windows Network. I always used applications users to log into it, but now I need to develop auditing mechanisms on the database and I guess using native SQL Server users and/or Windows users would ease programing this. Which way should I choose? Their use is conditioned to something?
>>
>>By the way, and I guess this would effect which kind of users to use, now we are working on the same LAN, but we are planning to do remote work, in other words most of the users will work from their homes.
>>
>>
>Luis, auditing requirements will vary, but here is something to keep in mind:
>
>If you have automated deployments, automated report jobs, automated database jobs, etc. - many places will require they run under control of a dedicated SQL Login (not tied to a Windows account) that has access just to the necessary database tables and nothing more. Yes, there are database shops that will fail audits
>
>That one becomes especially important if you're doing cross-server work.
>
>You know that old line, you can ask 10 economists a question and get 7 different answers. Same thing on auditing requirements. I can only offer what I've experienced, but I would start with the list of things above. And other topics might include which users/developers have access to dev, test, and production sites, etc.

Thanks for replying. Well the one condition all those app "new" users (in case I change my app with those in mind) is that they will only have access to the tables through the app, and additionally sending email using "Database Mail".

Currently all my app's users are registered in an app's table as well as their passwords (encrypted). To connect the app, I have created one SQL login (it is used in the ODBC string connection) that has access to all the app's tables and can do operations like insert, update, delete, as well as create temporary tables and cursor, and sending emails using "Database Mail".