I don't know what the UpdatedBy field is that you're referring to. I assume
it's either an Access thing, or a custom field.
In SQL Server, if we need historical data, we would either put a Trigger on
the Table and have it add to a log table, or perform all updates through a
Stored Procedure, and have THAT log the history record. Either way, you must
have another Table to store this historical data.
You have but a single column storing a single value in your Table, so it can
not store multiple values.
A very long time ago, I once used a system wherein I rotated the last (some
number) update history in a single field, seperated by delimitters. That
actually worked fine for researching updates that didn't need to know WHAT
was changed, just WHO and WHEN.
> When someone modifies a field in a table, I like to find out which
> field he/she changed.
[quoted text clipped - 4 lines]
> to be stored in a file or a table or something.
> Please help