>>>>>I have received an email from a customer IT on the subject of setting up user access to SQL Database for my VFP application.
>>>>>The following line in the message, especially the user of 'granular' is new to me.
>>>>>

>>>>>With other apps such as this we have used one account to authenticate to the db if auditing is not granular
>>>>>

>>>>>Could anybody explain what you think it means? TIA.
>>>>
>>>>Further to what has already been said, the word "granular" means at a very detailed level -- as in grains of sand.
>>>
>>>Yes, I understand the meaning of the word, in plain English. I just was not sure how it is applied it to the SQL Server security description. Thank you.
>>
>>Using a single account to access a database certainly makes configuration easy, but it makes auditing database use impossible or difficult at best.
>>
>>I always recommend all users use their own account - especially if they have write access to the database.
>
>Or, at least, have a method to capture a UserID of some type to put on the record they just updated/added/deleted

My application does that. Because besides the connection to the SQL Server the application has Users and User Groups. So each person has to enter his/her password in the application. And the application stores the user name in updated records and audit table, and so on. But I didn't want to argue with the customer DBA because this is like arguing with the wife <g>.