Log edits without showing username/timestamp
Is there a way to use the Log Entry feature without it logging the user or time stamp? I have two fields, "Related Job" and "Job History" in a table. Any time the key field of the table is modified...
Forum Discussion
I've hit a new snag which I'd love some help with if someone can.
I figured out what was being suggested above to log old entries. I have created a new table and the Action is now creating a new record into this new table any time the "Related Job" field in another table is modified. This helps me log any time "Related Job" is modified.
However here's where it's got a bit tricky. What I really want this to do is log every entry made into "Related Job", including it's current entry, as a new record but how do I do that?
The issue I'm having is that simply instructing the Action to "copy the old value" means that only the older entries are copied. The new one is not copied. If I add a second Action to copy the current entry, what happens is that it's now copying the new and old entries every time "Related Job" is modified, causing there to be duplicate entries because the current and old entries can sometimes be the same record.
I don't know if this is making any sense. In short, I want to log every record that is added to "Related Job" as a new record in a new table, including it's current entry, but only if that field gets modified.
I figured out what was being suggested above to log old entries. I have created a new table and the Action is now creating a new record into this new table any time the "Related Job" field in another table is modified. This helps me log any time "Related Job" is modified.
However here's where it's got a bit tricky. What I really want this to do is log every entry made into "Related Job", including it's current entry, as a new record but how do I do that?
The issue I'm having is that simply instructing the Action to "copy the old value" means that only the older entries are copied. The new one is not copied. If I add a second Action to copy the current entry, what happens is that it's now copying the new and old entries every time "Related Job" is modified, causing there to be duplicate entries because the current and old entries can sometimes be the same record.
I don't know if this is making any sense. In short, I want to log every record that is added to "Related Job" as a new record in a new table, including it's current entry, but only if that field gets modified.