There are several advantages to that approach - it works whether the record is created using a form or added at the table level. It also uses the system level authentication ID, so if you have users roaming across several workstations, it still captures the correct name. And it doesn't complicate your form design by using VBA to track things. The one thing it doesn't do is track who last changed the record. That can be done on an Access form, but you can't deal with changes made at the table level. SQL Server triggers are the best way of doing that IMHO.

Wendell

Colorado, USA