Editing query results, then appending to a table

[Access_Novice]

I don't have a sample I can upload. This is something I am just thinking about doing. I am try to create a billing record from timesheet data. I want to have a table to store timesheet information (tblTimesheets) and another table to store timesheet information that has been "posted" as being billed. This other table is called the tblBilled. The timesheet data would be uploaded every two weeks. Each time it is uploaded, the previously existing timesheet data would be deleted and replaced by the more recent year to date data (to take into account corrections to previous timesheets).



I would then initiate a query between tblTimesheet and tblBilled with a LEFT OUTER join. The result would be timesheet data from tblTimesheets that does not appear in tblBilled, meaning timesheet data that has not been billed yet. I might have to make some adjustments to the hours and $ in the query result as needed. When I'm done, I want to "post" this timesheet information so it is now recognized as having been billed. To do this, all I want to do is take those query results and append them to the table called tblBilled.

Is this possible? I'm sure I can take the query with the LEFT OUTER join and turn that into an append query, but the problem is that first I have to view the queried results and modify them. So I can't append them right away. So after I modify the queried results (e.g. decreasing the hours and cost), from this point, can I somehow append those modified query results to tblBilled?

Please keep in mind, that the timesheet data is uploaded every two weeks so it is constantly changing. Not only that, before each upload, the previously existing data needs to be deleted. So the data in tblTimesheets will change as new timesheet data is collected. Not only that, but timesheet entries from previous months could change due to timesheet corrections.

The data in tblBilled will also change as new timesheet data gets billed, however prior billed data will always remain the same.

[ranman256]

Erasing previous timesheets then loading them all over again sounds like a terrible idea. This is where youd have codes to show they were billed.

Instead, I would never delete the timesheet table, but rather, import all timesheets to a 'temp' area, compare the imported ones to the existing, remove sheets that have no change.
Now the temp table has 'modified' time, and new. Update timesheets and billing accordingly.

[Access_Novice]

Erasing previous timesheets then loading them all over again sounds like a terrible idea. This is where youd have codes to show they were billed.

Instead, I would never delete the timesheet table, but rather, import all timesheets to a 'temp' area, compare the imported ones to the existing, remove sheets that have no change.
Now the temp table has 'modified' time, and new. Update timesheets and billing accordingly.

The reason for deleting the timesheet table is because I can requery the data at anytime then upload it. Not only that, timesheet corrections occur every so often anyway so that is another reason. The timesheet source would come from another system so if I upload it to Access, do the necessary comparisons to what was previously billed there is no harm in deleting it because next time, I would start with a fresh query of timesheet data anyway.

So if I do the comparison, modify any numbers as necessary, could I still append that to the Billing table?