JOPO (just one person's opinion)...

Having a "known" structure (i.e., using the Append route) means all your
queries, procedures, reports, forms, relationships, ... can be set up and
left in place.

Using a Make table means starting over (many times), and will mess with your
relationships among tables.

It would help us help you more if we had some context for this decision.
Are you saying that you have something new each time, removing the
possibility of reusing (i.e., Append)? Or is the data actually going to be
used for updating ... that is, do you actually have to wipe out the "old"
version before loading in the new data?

More info, please...

--

Regards

Jeff Boyce
Microsoft Access MVP

Disclaimer: This author may have received products and services mentioned in
this post. Mention and/or description of a product or service herein does
not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"MJ" wrote in message
...
I am working on updates to a couple related databases (not linked by any
tables) and have a question about virtues of Make Table vs Append queries.

Make Table: I understand that this will create a NEW table where ever it
is
pointed,
so if that table already exists in the destination it
will be deleted, and
the new table written in its place.

Append : In this case I understand that it would require a little
more
"work" to
do same as Make Table, i.e. clearing out table before
appending data.

The 1st major difference, other than additional steps, I can see is if you
have a table structure you wish to retain the Append qry idea might be
more
favorable over the Make table qry.

Okay, now you database gurus...
(1) Are there any other advantages/difierences one over the other?; and
(2) What about database size impacts. grow/shrink, assuming the amount
of
data is fairly consistent from time to time of run?

--

MJ