From: Armen Stein on
On Tue, 29 Sep 2009 12:26:02 -0700, Jerry Whittle
<JerryWhittle(a)discussions.microsoft.com> wrote:

>Not with Access.
>
>If this is a hard requirement, you could upsize to something like SQL Server
>or Oracle. They both support auditing that can tell you who was messing with
>the data. They also support triggers at table level which could be used to
>record when a record was changed and by whom.

Yes. Keep in mind that SQL Server can only record *who* made the
change based on the SQL login. If you use Windows authentication,
you're fine - you can stop reading.

But if you use SQL Server authentication with a generic application
login (which is a simpler approach and preferred in some scenarios),
then you'll need to get the user another way. You can have each form
load the current Windows user into a ChangedByUser field in the table,
then have the trigger pick up the value of that field for the change
logging table, then clear the value in the main table so it doesn't
get picked up accidently the next time.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com