how do I combine several access 2007 files into one file

  • Thread starter Thread starter Distracted
  • Start date Start date
D

Distracted

I have several database files that I would like to combine into 1 major file.
What is the best way to do this? I am using office XP
 
"How" and "should" are two different issues.

Without a more specific description of the contents of those "several" and
the design of the "1", it'll be difficult to offer specific suggestions.

Generally, you could open a (?new) database file, link to all those
"several", and create queries to load the ?tables in your "1".

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
Distracted said:
I have several database files that I would like to combine into 1 major file.
What is the best way to do this? I am using office XP
Click to expand...

1) If it works, don't fix it.

2) If you're going to review how you distribute functionality between
files, remember that most experts say it's better to "split" your
database so that tables and their relationships are defined in one file,
with everything else in a linked front-end - or possibly several
different linked front-ends, so that you can provide different users
with what they need and no more.

3) You can use "Export" on the file menu to migrate (copy) objects like
queries and forms from the present database to a recipient database. Be
sure to migrate all dependent objects together.

Phil, London
 
The "file" is just a container for your objects like tables, queries forms,
reports. Taken you question just literally / at face value, you could just
choose one of the files/databases to be your final repository, can copy all
of those objects into it. You'd have a few things (e.g. relationships) that
you'd have to rebuild.

If you are looking to do more than that (i.e. combine data/tables etc ) then
that is a different thing, and you'd have to give more specifics regarding
what you want to do with those individual objects.
 
Philip,

Quick question.
I just created my first successful report. (the first few were not what
I wanted)
I did it in an old backup of my working data base.
Can I just export the report only to my working data base and not worry
about 'dependent objects'??
The report gets its data from a query that exists in the working database.

TIA
Rich W.
 
Rich said:
Philip,

Quick question.
I just created my first successful report. (the first few were not what
I wanted)
I did it in an old backup of my working data base.
Can I just export the report only to my working data base and not worry
about 'dependent objects'??
The report gets its data from a query that exists in the working database.

TIA
Rich W.
Click to expand...

If everything you say is true, yes. If you want to verify that the
query is the same, view both in SQL mode.

The way you're working makes perfect sense - get something tested
properly before incorporating it into a working database. One caution -
if you have split your database as described earlier, make sure you are
also working with a copy of the live backend - if you're linked to the
live data, the fox can be truly among the chickens...

Phil
 
Philip,

I do not have the data base split. Its 'My Work'
Its a record of what I did every day(very brief), Phone numbers, all the
printers, queues and such. I see no reason to split it as I am the only
one who uses it.
Good point tho.

Thank You
Rich W.
 
Back
Top