Moving Relationships Between Databases

[kh]

I've got a real general question on queries & relationships; I'm hoping this
is the right board to ask.

We've got a database file that opens in a proprietary program, although it
is a Microsoft Access (.mdb) format. The relationships between the modules
are specified in said proprietary program.

However, oftentimes we want to open the databases in Access & quickly create
other reports & queries as needed. To do so, we need to specify the
relationships between the different modules each time. Now, given the number
of different modules, this can be a lengthy task. Is there a way to specify
the relationships in one of the databases and then somehow quickly
copy/import the relationships into other databases as needed in order to
keep us from having to specify the same relationships over & over again.
Similarly, could you do the same thing with queries as well? Ideally, if you
could save relationships, queries, etc. & then import them into any
database, this would be ideal.

I tried doing a Google search, but I was having difficulties finding the
information. It does not help that I've done little work with MS Access,
which is probably readily apparent. Any assistance or nudges in the right
direction would be appreciated. Thanks.

 

[Jeff Boyce]

I'm not familiar with "relationships between ... modules" in Access. Do you
mean between tables?

Regards

Jeff Boyce
<Office/Access MVP>

 

[kh]

Yes, I mean tables.

Sorry about the incorrect lingo.

--
kh

I'm not familiar with "relationships between ... modules" in Access. Do
you mean between tables?

Regards

Jeff Boyce
<Office/Access MVP>

 

[Jeff Boyce]

If your backend database already has relationships established (?via the
Relationships window), I would think that opening a new database (.mdb file)
and linking to that database & those tables would show the (pre-)existing
relationships. What happens when you do this?

Jeff Boyce
Microsoft Office/Access MVP
Microsoft IT Academy Program Mentor

Yes, I mean tables.

Sorry about the incorrect lingo.

 

[kh]

I haven't tried this yet, but I'll give it a whirl. (Another more important
project has come up, so this has now been pushed to the back burner.) As I
said, I'm relatively new to Access, so I'll have to read up on how to do
what you've described.

Thanks for your assistance.

kh