Why use another table? Add Archive Yes/No and ArchiveDate fields. Then just
flag when it is archived and update the ArchiveDate field.

Signature
KARL DEWEY
Build a little - Test a little
Karl, thanks for responding. However, I don't fully understand your
response, particularly the Yes/No option. But to revise on what I do gather
from your response, I could use the same table, create an archiveNotes field,
can append the current date as header when button is clicked to move the
notes being archived into this new archiveNotes (memo type) field.
If this sounds good, theory, I'm still not proficient enough w/ Access yet
to invoke the actions. Can you lend that help?
> Why use another table? Add Archive Yes/No and ArchiveDate fields. Then just
> flag when it is archived and update the ArchiveDate field.
[quoted text clipped - 9 lines]
> > contents of the Notes field in the employee record - moving that data to a
> > new record in the associated archivednotes table (adding a date/time stamp).
KARL DEWEY - 06 Sep 2007 18:50 GMT
Not quite what I meant. I misread your orginal post thinking you had 1-many
employee-notes tables.
Have Notes table with the following fields --
NoteID - autonumber - primary key
EmployeeID - foreign key
NoteDate - DateTime
Note - memo
Have an Event or macro that is triggered when you double-click the NoteDate
field to append a new record and set the current date into the NoteDate field
of the new record.
Use a form (employee)/subform (notes in descinding date order) to display
the information.

Signature
KARL DEWEY
Build a little - Test a little
> Karl, thanks for responding. However, I don't fully understand your
> response, particularly the Yes/No option. But to revise on what I do gather
[quoted text clipped - 17 lines]
> > > contents of the Notes field in the employee record - moving that data to a
> > > new record in the associated archivednotes table (adding a date/time stamp).
jehmsit - 06 Sep 2007 18:56 GMT
Thanks. That's exactly what i wanted to do.
> Not quite what I meant. I misread your orginal post thinking you had 1-many
> employee-notes tables.
[quoted text clipped - 33 lines]
> > > > contents of the Notes field in the employee record - moving that data to a
> > > > new record in the associated archivednotes table (adding a date/time stamp).