If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
Temporary Tables for Importing/Exporting
Thank you for the assistance John.
Brian "John W. Vinson" wrote: On Tue, 10 Feb 2009 19:53:02 -0800, Brian Carlson wrote: John: Given that it should only be myself and another user, this should work for me. Other than this, do you see any problem with the use of temporary tables? Keeping track of what's been added and what hasn't becomes a real hassle and requires care, but other than that, no. An additional follow-up question; Should the records in the temporary table be erased after exporting to the backend? It seems that they would need to be. I imagine that I could do a delete query to manage this. Thank you for your assistance. I can make arguments for either of two approaches: create an all new .mdb file for the temporary database (by copying an empty template database, or empty except for lookup tables) and deleting the entire database after it's appended; OR adding a date/time timestamp field and archiving the offline additions (using a date selective query in the transfer), just in case you need to go back and find out where and when a particular record was added (and perhaps re-add them). You'll need to decide which - or some other! - method suits your business needs. -- John W. Vinson [MVP] |
|
Thread Tools | |
Display Modes | |
|
|