Is there a way of joining tables in a data base without using the
"relationships" feature? I have several tables of similar information and
want 1 big database.

Why? That defeats the whole point of using a relational database. It is
also poor design. Why would you want to do this? You can certainly use
data from multiple tables in forms, queries, and reports.

Rick B




"KitV" <(E-Mail Removed)> wrote in message
news:F252667F-57D8-42DD-80A5-(E-Mail Removed)...
> Is there a way of joining tables in a data base without using the
> "relationships" feature? I have several tables of similar information and
> want 1 big database.

Why do you way that, Rick?

If the tables have similar information, it may well be appropriate to store
the information in a single table. For instance, if the original designer
had a different table for each region, it would make more sense to add a
Region column and store everything in one table.

Kit: you'll have to provide a little more detail.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(No private e-mails, please)


"Rick B" <Anonymous> wrote in message
news:#bWDrnk#(E-Mail Removed)...
> Why? That defeats the whole point of using a relational database. It is
> also poor design. Why would you want to do this? You can certainly use
> data from multiple tables in forms, queries, and reports.
>
> Rick B
>
>
>
>
> "KitV" <(E-Mail Removed)> wrote in message
> news:F252667F-57D8-42DD-80A5-(E-Mail Removed)...
> > Is there a way of joining tables in a data base without using the
> > "relationships" feature? I have several tables of similar information
and
> > want 1 big database.
>
>

Good point, Doug. I assumed it was set up correctly in the beginning and he
wanted to change it to a worse layout.

Rick B

"Douglas J. Steele" <NOSPAM_djsteele@NOSPAM_canada.com> wrote in message
news:%23btWTxk%(E-Mail Removed)...
> Why do you way that, Rick?
>
> If the tables have similar information, it may well be appropriate to
store
> the information in a single table. For instance, if the original designer
> had a different table for each region, it would make more sense to add a
> Region column and store everything in one table.
>
> Kit: you'll have to provide a little more detail.
>
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (No private e-mails, please)
>
>
> "Rick B" <Anonymous> wrote in message
> news:#bWDrnk#(E-Mail Removed)...
> > Why? That defeats the whole point of using a relational database. It
is
> > also poor design. Why would you want to do this? You can certainly use
> > data from multiple tables in forms, queries, and reports.
> >
> > Rick B
> >
> >
> >
> >
> > "KitV" <(E-Mail Removed)> wrote in message
> > news:F252667F-57D8-42DD-80A5-(E-Mail Removed)...
> > > Is there a way of joining tables in a data base without using the
> > > "relationships" feature? I have several tables of similar information
> and
> > > want 1 big database.
> >
> >
>
>

On Fri, 14 Jan 2005 06:37:05 -0800, "KitV"
<(E-Mail Removed)> wrote:

>Is there a way of joining tables in a data base without using the
>"relationships" feature? I have several tables of similar information and
>want 1 big database.

An Append query will add the records in one table as new records in
another table; you should consider creating a "master" table to hold
all this data, if indeed the tables are of similar structure; run an
Append query for each table that you want to include into the new
table.

If you want to keep the tables separate (probably not a good idea but
just in case), but combine them for searching or display, you can use
a UNION query; see the online help for UNION.

John W. Vinson[MVP]