5 pts.
 Access database management
Hi guys I am managing a database and need to know if there is away of moving 'completed' records into another database but keep them linked. Senario is: We have records of pieces of work coming into the office and which take about amonth to complete the cycle. My query is instead of having this database then filling up with completed and uncompleted records, how would you move the completed lines into a second databse, yet have it linked? I would think i would need part of it that states eg 'Record Complete' where would input a 'Y' to signify this. Then what would i need to do to move that line into a second database for completed records? Any suggestions or solutions from others that have similar projects much appreciated. Tim Anderson

Software/Hardware used:
ASKED: August 21, 2008  8:30 AM
UPDATED: August 21, 2008  2:42 PM

Answer Wiki:
Simply link the table (Get External Data - Link) from the history database into your current database. Say the table in current is Work and you would link WorkHistory from the history database. Now both databases are in you main application database. Then as the work is compelete, you could make an append query to append the records from the Work table to the WorkHistory table and then a delete query to delete the records from the Work table. You could make a union query called AllWork like this: Select * from Work Union Select * from WorkHistory. Now when you access that query for example in a report or look up form, you will have all records - both current and history.
Last Wiki Answer Submitted:  August 21, 2008  2:25 pm  by  Jaideep Khanduja   8,200 pts.
All Answer Wiki Contributors:  Jaideep Khanduja   8,200 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _


 

To give you a good view of what is happening to your records, you would be better adding the following fields to your “working” database
1. A status i.e. N=New Record, I=Incomplete, C=Complete
2. A user stamp – I assume that you have user logins in your database that you can record when a transaction line / record is updated.
3. A date/time stamp – the last date/time that the record was updated.

Using these three in addition to the above will give you greater management over which records need to be updated, and also enhance your ability to track and filter data.

 325 pts.