Linked Table Clarification

[GIraffe]

I had overlapping data from one DB to another in a linked table. I received
a suggestion to have all my tables in one DB (backend) and all my forms, etc.
in a separate DB (frontend). I haven't done this yet, so I don't know, but
won't I have the same problems with overlapping data? So I need
clarification concerning linked tables. [P.S. - I didn't continue the
previous thread as I thought it was too old.]

Here's one I'm doing:
Currently, I have a files DB and a pubs DB.
I have a location table ("where will I find the file or pub") that is
currently linked.
I have 1 form for my files (w/ subform for location) & 1 form for my pubs
(w/ subform for location) [Different information requirements on each].
I enter a record on my file form (we'll call it ID1) and choose my location.
then I enter a record on my pubs form (also ID1) and choose my location. My
pubs location overwrites my files location.

Since I'm working off two different forms, won't I have the same overlapping
problem even if I split the tables in one DB and my forms, etc. in a second
DB?

Thanks for the clarification.

G

 

[Jeff Boyce]

see comments in-line below

I had overlapping data from one DB to another in a linked table. I
received
a suggestion to have all my tables in one DB (backend) and all my forms,
etc.
in a separate DB (frontend). I haven't done this yet, so I don't know,
but
won't I have the same problems with overlapping data?

If all your data is in one place and all your forms (etc.) are someplace
else, how could you have "overlapping data"?

Maybe you'd better clarify what YOU mean by "overlapping data"...

So I need
clarification concerning linked tables. [P.S. - I didn't continue the
previous thread as I thought it was too old.]

Here's one I'm doing:
Currently, I have a files DB and a pubs DB.
I have a location table ("where will I find the file or pub") that is
currently linked.
I have 1 form for my files (w/ subform for location) & 1 form for my pubs
(w/ subform for location) [Different information requirements on each].
I enter a record on my file form (we'll call it ID1) and choose my
location.
then I enter a record on my pubs form (also ID1) and choose my location.
My
pubs location overwrites my files location.

How? As in "how can your 'pubs' record overwrite your 'file' record? Are
you storing them both in the same place? Where are you storing them?

It all starts with the data. We can't see yours, so we can only guess what
data structure you might be using.

Since I'm working off two different forms, won't I have the same
overlapping
problem even if I split the tables in one DB and my forms, etc. in a
second
DB?

Forms are not tables. Forms display data. Tables store data. More
specific information about your table structure may lead to more specific
suggestions.

 

[GIraffe]

Hi Jeff:

You are correct, re-reading now, I see I wasn't clear. Let me try to
explain better what is happening.

I have 2 separate DBs - Pubs & Files, with a linked Location table
(currently residing in the Pubs DB). Specifically:

Pubs DB
TblPubs
PubID
Title
Author

TblLoc [Linked table]
LocID
PubFileID
Room

FilesDB
TblFiles
FileID
FileName

My relationships are
TblPubs.PubID > TblLoc.PubFileID &
TblFiles.FileID > TblLoc.PubFileID

In the Pubs DB, using a form, I enter a record in TblPubs (we'll call it
PubID 1) and choose a room (we'll say 200) in TblLoc. Then if I add a new
record in Files DB, using a form, I enter a record in TblFiles (we'll call it
FileID 1) and choose a room (we'll say 100).

What's happening, and what I mean by overlapping data is, if I go back in to
the Pubs DB and call up PubID 1, the room location has been changed from 200
to 100.

Is this a clearer explanation?

Thanks for your help.

G

see comments in-line below

I had overlapping data from one DB to another in a linked table. I
received
a suggestion to have all my tables in one DB (backend) and all my forms,
etc.
in a separate DB (frontend). I haven't done this yet, so I don't know,
but
won't I have the same problems with overlapping data?

If all your data is in one place and all your forms (etc.) are someplace
else, how could you have "overlapping data"?

Maybe you'd better clarify what YOU mean by "overlapping data"...

So I need
clarification concerning linked tables. [P.S. - I didn't continue the
previous thread as I thought it was too old.]

Here's one I'm doing:
Currently, I have a files DB and a pubs DB.
I have a location table ("where will I find the file or pub") that is
currently linked.
I have 1 form for my files (w/ subform for location) & 1 form for my pubs
(w/ subform for location) [Different information requirements on each].
I enter a record on my file form (we'll call it ID1) and choose my
location.
then I enter a record on my pubs form (also ID1) and choose my location.
My
pubs location overwrites my files location.

How? As in "how can your 'pubs' record overwrite your 'file' record? Are
you storing them both in the same place? Where are you storing them?

It all starts with the data. We can't see yours, so we can only guess what
data structure you might be using.

Since I'm working off two different forms, won't I have the same
overlapping
problem even if I split the tables in one DB and my forms, etc. in a
second
DB?

Forms are not tables. Forms display data. Tables store data. More
specific information about your table structure may lead to more specific
suggestions.

Thanks for the clarification.

G

--
Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Margaret Bartley]

Hi Jeff:

I have 2 separate DBs - Pubs & Files, with a linked Location table
(currently residing in the Pubs DB). Specifically:

Pubs DB
TblPubs
PubID
Title
Author

TblLoc [Linked table]
LocID
PubFileID
Room

FilesDB
TblFiles
FileID
FileName

My relationships are
TblPubs.PubID > TblLoc.PubFileID &
TblFiles.FileID > TblLoc.PubFileID

In the Pubs DB, using a form, I enter a record in TblPubs (we'll call it
PubID 1) and choose a room (we'll say 200) in TblLoc. Then if I add a new
record in Files DB, using a form, I enter a record in TblFiles (we'll call
it
FileID 1) and choose a room (we'll say 100).

What's happening, and what I mean by overlapping data is, if I go back in
to
the Pubs DB and call up PubID 1, the room location has been changed from
200
to 100.

It looks like when you add a new record in Files DB, you are not adding a
new record in TblLoc, but rather, opening the existing record, and changing
the Room from 200 to 100.

That is one of many possibilities.

Another is that when you go back to the Pubs DB and Call up PubID 1, you are
not properly linking up to the original TbleLoc that you used when you
entered the data.