Moving data from table to another

[elli]

Hi there,
What's the simplest way to move data from one table to another? I tried with
compination with make table query and delete query so that I made a new
table from data (marked with boolean) and then delete query to move the
objects from tha main table. Works all right, but it clears the new table
also. I need the data removed to stay there.
I'm working with a customer database, where old customers should be removed
but data saved.....

Any hints?

elli

 

[John Vinson]

I'm working with a customer database, where old customers should be removed
but data saved.....

Simplest way is to put a yes/no Active field in the table; simply set
it to False when the customer is "removed", and use queries to select
only active (or inactive) customers. No moving of data is required.

If you want to do so anyway, a combination of an Append query and a
Delete query will work.

John W. Vinson[MVP]

 

[elli]

Hello John
And thank You very much for your answer. Nice suggestion, but in the years
to come the non-active data will grow so huge that it's not an option.
So I guess I'll have to start to work with the append -queries....
I'm not so sure what those do.....
Take care

elli

 

[Douglas J. Steele]

Define "grow so huge".

If you're talking about hundreds of thousands of rows, you might have reason
to worry. If it's only going to be hundreds, or even thousands, no big deal.

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)

 

[Larry Daugherty]

Wow! The marketing gurus would tell you that you're nuts for trying
to purge the old customer data. Inactive customers are referred to as
the "dead file" and there are several strategies for re-activating
them or selling to them in some way. The other pearl of wisdom is
that it's much more costly to get a new customer than to sell to an
existing or former customer.

All that being said, at what rate is your total customer base growing?
When do you expect your data tables to approach the 2 gigabyte limit?
My guess is that by the time you hit that limit the limit will be 4
gigabytes or greater. You could also use MSDE or SQL Server as the
back end and pretty well go on forever.

I suggest a strategy that incorporates the one John suggested: Create
a Boolean field for Status. If there is no handy time stamp field in
your current design, add one so that you can tell when this customer's
account was pronounced "dead". With the status field, you can
easily address just the active accounts. If your database should ever
approach the size limit, save a copy and label it something like
'Golden Archive as of "DATE" with customers records back to "DATE"'.
Then, pick a cut-off date in your current database and delete all
customer records that were marked "dead" on or before that date.

HTH