copy a database without the data

[Katwoman]

I would like to copy a database in access 2003 without the data stored. I
currently have a database called 2009 and want to make one exactally like the
2009 for 2010.


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...ce8&dg=microsoft.public.access.tablesdbdesign

 

[Jerry Whittle]

It's almost always a mistake to make a different database for each year,
month, etc. What happens when someone wants to compare and contrast 2009 with
2010? You are usually better off having a date or Year field for the records
so that you can do queries and reports based on the year.

As far as emptying out a database of records, the first thing to check is if
referential integrity is enabled. Do this in the Relationships Window. If so
you will need to delete the records from the child tables first then work up
to the parent tables unless you have cascade delete enabled.

Let's say that you don't have referential integrity enabled on any
relationships in the Relationships Window. You still might run into a problem
if you have certain kinds of lookup fields enabled at table llevel.

Your best bet is to first and foremost make a copy of your database. Then
using the copy, open up each table and delete all the records. You can select
all records by clicking on the upper left corner of the table. Then hit the
delete key and say Yes to warning. Hopefully you won't run into any problems.

 

[John W. Vinson]

I would like to copy a database in access 2003 without the data stored. I
currently have a database called 2009 and want to make one exactally like the
2009 for 2010.

This is A VERY BAD IDEA.

Dates are data and should be stored in your table as data. If you need to
compare data from 2009 to 2010, or generate a report for October 2009 through
March 2010, you'll be in real trouble.

That said... create a new empty database and use File... Get External Data...
Import to import everything. Choose the option on the Tables tab "design view
only".

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...ce8&dg=microsoft.public.access.tablesdbdesign

This isn't really a "suggestion to Microsoft" - just post questions like this
as questions, we'll answer them.

 

[Katwoman]

I tried this and what happens is I loose the data in the 2009 database as well.

 

[Gina Whipp]

Katwoman,

You have already been told why it's not a good idea to have duplicate
database for each year so I won't go into that but... Are these linked
tables??? Because judging by your description as to what is happening when
you delete records it sounds like it is. You would need to create a new
database and import the tables from the back end and THEN delete the data.
--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[John W. Vinson]

I tried this and what happens is I loose the data in the 2009 database as well.

Is it a Split database (with the tables in a backend and the forms etc. in a
frontend)? If so you need to make a copy of the *BACKEND* and empty the tables
in the copy, then relink the frontend to the new backend.

I hope you had good backups before deleting.

 

[Katwoman]

Thank this worked

Katwoman,

You have already been told why it's not a good idea to have duplicate
database for each year so I won't go into that but... Are these linked
tables??? Because judging by your description as to what is happening when
you delete records it sounds like it is. You would need to create a new
database and import the tables from the back end and THEN delete the data.
--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Gina Whipp]

You're welcome!

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Ken Snell MVP]

Katwoman,

You have already been told why it's not a good idea to have duplicate
database for each year so I won't go into that but... Are these linked
tables??? Because judging by your description as to what is happening
when you delete records it sounds like it is. You would need to create a
new database and import the tables from the back end and THEN delete the
data.

Or, check the "Definition Only" option on the Options button for the tables
before importing the tables.

 

[Gina Whipp]

Ken,

She said she tried that and it didn't work. Of course, she might have been
trying it on linked tables.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm