By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,082 Members | 2,108 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,082 IT Pros & Developers. It's quick & easy.

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

P: 5

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?
May 21 '08 #1
Share this Question
Share on Google+
2 Replies

Expert 100+
P: 407

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.

May 21 '08 #2

Expert Mod 15k+
P: 31,494
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?
May 22 '08 #3

Post your reply

Sign in to post your reply or Sign up for a free account.