create a duplicate database

[Julie]

I need to create a new database from/similar to an existing one. The existing
one is very intense with many things no longer need (or never were needed).
Since it is so intense I would like to recreate the existing one and edit the
crap out of it. Everytime I copy the database, even with a different name and
location, they stay connected. Meaning if I change things in the copy it
changes in the original. Is there a way that I can create a duplicate to the
existing database and make changes to the dupe that won't affect the original?

Part of the problem is I only work on this in between priority work, and
since this is a constantly changing dsatabase (several employees use it
daily) I can't leave it hanging.

Thank you

 

[Jeff Boyce]

Julie

It sounds like you might have a front-end application (.mdb) file that is
linked to back-end tables (in Access, in SQL-Server, in DB2, in ...). When
you copy the front-end, you are copying the links.

If you don't want the new front-end to be affecting the existing back-end
data, delete the linked tables in the new copy. But then none of your
forms, queries, etc. will work!

What are you going to use as a data source for your new database? (I'd
suggest making a copy of the current data, then linking to that copy for
design/development/testing.)

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[John W. Vinson]

I need to create a new database from/similar to an existing one. The existing
one is very intense with many things no longer need (or never were needed).
Since it is so intense I would like to recreate the existing one and edit the
crap out of it. Everytime I copy the database, even with a different name and
location, they stay connected. Meaning if I change things in the copy it
changes in the original. Is there a way that I can create a duplicate to the
existing database and make changes to the dupe that won't affect the original?

Part of the problem is I only work on this in between priority work, and
since this is a constantly changing dsatabase (several employees use it
daily) I can't leave it hanging.

Thank you

What's "connected"??? It sounds like you may just be copying a shortcut to the
database, rather than the .mdb file itself.

Try creating a new database by just opening the Access program itself - no
shortcuts, no database specified - and use File... Get External Data... Import
to import whatever you want from the existing database.

I would VERY STRONGLY recommend going to a split database (Tools...
Utilities... Database Splitter). This will let you keep the data in one shared
backend database, and each user gets their own copy of the "frontend" with
links to the tables, and all of the forms, reports, queries etc.

This will (among other benefits) let you clean out the old unneeded objects in
your own copy of the frontend; when it's all nice and tidy you can distribute
a copy to everyone, without interfering with the data in the backend database.

John W. Vinson [MVP]

 

[Julie]

Yes you are correct it is a mdb and you just help me understand why the
reports etc don't work on one that someone unlinked .

The data is entered daily by different people as issues that need research,
come up. So maybe I'm not understanding when you ask what I'm using as my new
data source. But are you saying that I can make just a normal copy of the
exsisting database then create a blank new one with a different name and
location, link to the copy and the new one would have all the same info yet
not affect the original?

 

[Julie]

I was sure I was not using a shorcut and I had tried copying from Access but
still stayed connected. I think the answer I received above cleared that part
up.

I will take your suggestion about splitting the database and will look at
other threads that discuss it. Ive created a few databases over the past
several years, but am not an expert by any means. I'm looking for the
simplest way. thank you so much for the advice

 

[Jeff Boyce]

Julie

As John is pointing out, "splitting" your database means putting the tables
(only) in one .mdb file, and putting everything else (forms, queries,
reports, ...) in another.

Since you wish to make changes to the entire database, I think you'll need
to have a copy of the back-end (tables only) AND the front-end (everything
else). Then you'll need to link from your (copy) front-end to the tables in
your (copy) back-end.

Since you'll be the only person connected to the data in the (copy)
back-end, the development and testing you do will only affect that (copy).

Does this get you closer to what you need to do?

Regards

Jeff Boyce
Microsoft Office/Access MVP