Moving Records Between Tables

LowkeyTech

New member
Local time
Today, 22:21
Joined
May 7, 2014
Messages
1
I have been tasked with creating a simple database for work.

Basically the table tracks the progress of various employment checks. So example headings are Name, CRB, Occupational Health etc. Now basically, once all the checks are completed, I need the record to be moved to another table named 'Live'.

Is there any easy way to achieve this, or will i have to manually move each record once the checks have been completed.

Apologies if this is a really simple question, it's been years since I used Access properly.

Thanks in Advance.
 
Hello LowKeyTech, Welcome to AWF :)

Just wondering why do you need to move data between tables? All you need is to modify the Recordsource of the Form or something to show only the records that have all "Test" completed. You do not have to copy/move records between tables. This is my opinion. You can wait for others opinion too.

Good luck with your project.
 
one other thing

very few databases are "simple".

A database with only a few tables is similar in a some respects to a spreadsheet - but one which uses a lot of macros, and vba code to limit how users interact with the spreadsheet. A spreadsheet including such features would not be simple either.

Unlike a spreadsheet, though you just should not expect to build a database without a lot of careful consideration about what you wish to achieve.

even "name" (employeename) requires consideration. It is often unreliable to rely on a name being unique. Larger organisations could well have employees with the same name. I am sure most people would recommend adding a numeric "employeeID" to your tables to manage the employees. And most would advise you not to use just the column name "name" - as although not illegal, name is a reserved word in access used for other purposes, and a field called name might be confusing, or cause errors.
 
One does not move records from one table to another to indicate its status. This is using structure to store information and is always a wrong design concept.

All that is required is another field in the original table to indicate the Live status.
 

Users who are viewing this thread

Back
Top Bottom