>>What I currently have is almost exactly what you have explained so far.
>>
>>>Then, when a user makes any change to a table, another table gets an entry of the value before and after the change; for each changed field. Therefore, this Audit Table is what the application uses to report of what changes were done to a table/field and who did it. The auditing routine in itself is part of the Biz Object of the application.
>>>
>>In other words, before saving the changes for each table (remote view), the Biz object opens the audit view where it saves all the fields changed (both old and new values) in that table together with the user id, date/time and workstation. Am I right? If not, please, correct me.
>>
>>>I hope it answers you question.
>>
>>Thanks.
>
>You are right, as far as opening the audit table and updating it with the changes.
>But I use Cursor Adapter, not remove views.
>UPDATE. I don't save the workstation in the audit table. Just the username who is using the application, and of course, date and time.

My perspective was never from VFP's side but SQL Server's, using triggers, that's why I was asking whether to use SQL logins or Windows users. Now I see that the way you do it makes it much more easy to develop it. Thank you very much!

On the other hand, you say you use Cursor Adapters instead of remote views. Would you tell me what are the advantages of the first ones over the second ones?