rr*****@yahoo.com (Rich N) wrote in message news:<24**************************@posting.google. com>...
Thanks Pieter, but I don't think you understood my question (or maybe
I wasn't clear). I understand how to do it. The database is split:
I don't know whether to do the Make Table Query, etc, in the "regular"
database, or the .be database
pi********@hotmail.com (Pieter Linden) wrote in message news:<bf************************@posting.google.co m>... rr*****@yahoo.com (Rich N) wrote in message news:<24**************************@posting.google. com>... I want to move several records from one table to a new table. My
database is set up so that there's the "regular" database, and the
".be" database. In which do I use the Make Table Query?
Use an append query to copy the records to the new table, and then a
delete query to remove the old ones. Be sure to keep the criteria the
same. And if you really want something like robustness, wrap the
whole thing in a transaction so if one part fails, it all fails.
Correct. My mistake. Totally misunderstood your question. So...
The table would go in the back end if:
1. you wanted everyone using the DB to have access to the table.
2. the table was permanent.
Put it in the front end if:
1. it's a "work" table that you're going to throw away/delete the
contents of on a regular basis. (Actually, if it's one of those, put
it in a third db, link to that DB in code and then just delete your
connections and the temp db. See Tony Toews's site for an example.
2. (kind of an expansion on 1) Everyone will need separate copies of
the dataset to play with at once.
Hope this clarifies things a little.
pieter
