copying database for backup

I have a database with 3 years of data - I would like to save it - make a
copy and delete out all of the data to save the old and start fresh with 2010
data- the database is Split into a backend and front end( that is confusing
enough in itself)

Just wondering for the best steps to make a copy to store for prior 3 year
database. - new database for 2010 - some of the tables will retain their
records - ex. customers etc. others with transcations will/should only have
2010 data.

Not sure if make a copy of front end and backend for Prior to 2010
and then a New front end and back end for 2010 data

we would like to occationally go back and review the old data??

Any standard steps for doing this would be great - I would think that this
should be a pretty common thing??
Thanks,
Barb

Why on earth do you want to get rid of historical data?

This would definitely NOT be a common thing.

If you don't want old data on reports and forms, just filter them to show
current info. Allow users to select a data range for reports.

data- the database is Split into a backend and front end( that is
confusing
enough in itself)
How is this confusing? Tables with data in the back end, everything elso in
the front end which can be distributed to several people. They all see the
exact same copy of the data in the back end. If everyone had their own
database with everything they would only see changes they have made to their
own copy.

Mich

"babs" wrote in message
...
I have a database with 3 years of data - I would like to save it - make a
copy and delete out all of the data to save the old and start fresh with
2010
data- the database is Split into a backend and front end( that is
confusing
enough in itself)

Just wondering for the best steps to make a copy to store for prior 3 year
database. - new database for 2010 - some of the tables will retain their
records - ex. customers etc. others with transcations will/should only
have
2010 data.

Not sure if make a copy of front end and backend for Prior to 2010
and then a New front end and back end for 2010 data

we would like to occationally go back and review the old data??

Any standard steps for doing this would be great - I would think that this
should be a pretty common thing??
Thanks,
Barb

If you take the time to read what was posted , the actual requirement was,
"... I would like to save it - make a copy and delete out all of the data
*to save the old* and start fresh with 2010 data-"

So, no, there's no getting rid of historical data going on at all. It's
being archived out of the active database. While it is perhaps more common
NOT to do it, archiving older records is definitely something that is useful
and a standard practice when the circumstances warrant it. This may not be
one of those cases, of course, but we don't really know enough about the
business being handled to be able to say one way or the other.




"M Skabialka" wrote in message
...
Why on earth do you want to get rid of historical data?

This would definitely NOT be a common thing.

If you don't want old data on reports and forms, just filter them to show
current info. Allow users to select a data range for reports.

data- the database is Split into a backend and front end( that is
confusing
enough in itself)
How is this confusing? Tables with data in the back end, everything elso
in the front end which can be distributed to several people. They all see
the exact same copy of the data in the back end. If everyone had their
own database with everything they would only see changes they have made to
their own copy.

Mich

"babs" wrote in message
...
I have a database with 3 years of data - I would like to save it - make a
copy and delete out all of the data to save the old and start fresh with
2010
data- the database is Split into a backend and front end( that is
confusing
enough in itself)

Just wondering for the best steps to make a copy to store for prior 3
year
database. - new database for 2010 - some of the tables will retain their
records - ex. customers etc. others with transcations will/should only
have
2010 data.

Not sure if make a copy of front end and backend for Prior to 2010
and then a New front end and back end for 2010 data

we would like to occationally go back and review the old data??

Any standard steps for doing this would be great - I would think that
this
should be a pretty common thing??
Thanks,
Barb