>Hello all,
>
>I want to create a log table so I can trace what the users are doing. What should go in that table. I guess more than 1 table will be necessary.
>
>How far should I go with this? I mean I could create a table that contains the name of my forms. and then in the main table have a reference to the form that was accessed or should I go the easy way considering it would be enough and only have 1 table containing only some chars for each action undertaken by the users.
>
>Suggestions?

At Bata/Bolivia, over time I included several pieces of information, in different tables.

An audit trail (what data was changed); we considered this important to be able to see who was responsible for some weird change.

Login and logout - this allowed us to see what users were currently connected. Though not with great precision, because if a computer crashed, no logout was generated.

Opening a form - we wanted an analysis of what forms were actually used, as a first step to withdrawing obsolete forms. (The system had over 300 forms when I left.)

The audit trail, of course, was by far the biggest one. In one of my articles for UTMAG I outline the basic steps to create one, in case you use Visual FoxPro tables, and don't want to purchase specific tools for this.

Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)