Archive records via command button (append to different table within database)

[Cara Murphy]

Hi,

I am looking to use a button on an issues database that will allow me to archive issues that are closed, once all of the information has been updated. In this sense, I want the issue to be available for final input after it has been "closed", and use a command button to "delete" it (append the record to a table called ArchiveIssues and remove it from the table called Issues).

Can you please advise what my options are to facilitate the archiving process?

[JustJim]

Hi,

It seems to me that you don't need two tables, you just need a field in the Issues table that determines if a record is archived or not. Then the underlying query for any forms/reports you write just check for this field and don't include those records.

Jim

[NeoPa]

That's good advice Cara.

Can you explain more clearly what you're after though? I'm not sure what you're having difficulty with. Is it actually implementing the concept you already seem to understand pretty well?