If there could be more than one record for Tag_Misc, Tag_Failure_Mode, and
Tag_Format, those tables need to one-to-many. If they are one-to-one there
can be only one Tag_Misc record for each Tag. In the Relationships window,
one-to-many will appear (in Access 2003 and earlier, anyhow) with a 0 on one
end of the relationship line, and an infinity symbol on the other.
The problem I see is that it seems you are attempting to link the primary
keys of your tables. Using Tag_Misc as an example, you should have:
tblTag:
* TagID
Description
Tag_Cat (category)
Function_code
tblTag_misc
*Tag_miscID
TagID (linking field to tblTag)
manufacturer
misc fields....
It may be possible under some specific circumstances to link the PK of one
table to the PK of another for a one-to-one. If so, it would work onlyif
the PK field of the linked table is not autonumber. I'm not sure if itwill
work even in that case, as on the rare occasions I have used one-to-one I
have designed the table as if for one-to-many, but with a unique index onthe
linking field.
You can set the Required property of the linking field to Yes, but that only
means (unless I am missing something) that if there is a record it must have
a value in that field. If you want to require Tag_misc records for each Tag
record I think you will need to enforce that at the form level, or at least
in some way other than requiring a value in that field.
Form/subform is the best way to set this up. It would be possible to append
values in other ways, but for day-to-day data entry it is unlikely it would
make much sense to take that approach. A form based on a query including
several table may not be updatable. For more:
http://allenbrowne.com/ser-61.html
On another note, I would not use Tag as a table or field name, as it is a
property of forms, reports, and controls. If you use it you would haveto
enclose it in square brackets, or you could get some unexpected results. I
have suggested tblTag as the table name, and TagID as the field name, butyou
can choose what you like. For more on Reserved words:
http://www.accessmvp.com/JConrad/accessjunkie/resources.html#Reserved...
I have found Allen Browne's Problem names and reserved words in Access tobe
especially helpful.
Thank you guys. I'll give you more details.
I am in the design phase of a project, and my client wants me to
import all my data when all is as-built. My client has a database for
all his needed info, so I just used that database structure as a basis
for my design. I also added some new tables for design specific data,
and some other stuff that won't go to my client.
There is the master tag table. This holds the main list of records.
Then supporting tables to give more information about different kinds
of tags.
First, the tables: I've not listed all the fields, but the most
relevant ones.
Tag:
*Tag
Description
Tag_Cat (category)
Function_code
...
Tag_misc:
*tag
manufacturer
misc fields....
The tag_misc table is 1 to 1. All tags should have information in the
tag_misc table. I know I then should have all that information in one
table, but since the original client structure needs to be maintained
I chose that design. And this has worked for a while, so I thought
it'd still work.
The tag_failure_mode table should contain data for most tags, but not
all. I chose to have a record in there for all tags regardless, as i
thought that may be easier to maintain. This is based on the tag!
function_code field.
The tag_format table should have data for tags of certain tag!tag_cat
values (br, in and te type tags). Once again, most of my tags are in
this category, so I chose to have all tags in this table too.
So I have used a query to gather up all the relevant fields for my
users (they are conservative and like their big excel-like datasheets)
in one big list.
My client made a change in his underlying database recently, so I
thought I'd take the opportunity to re-work my database as well.
trying to get rid of the big queries and relying more on forms, and
also finally linking the database (we've all been working on the same
file up until now).
So after these changes I get the message that a relevant record needs
to exist in the CHILD database, the Tag_failure_mode table in my
instance.
If it is like you say then I find it strange that this has worked
before, really. I see how it would work like you say, but then how did
it work this long? It was after I linked the database and added the
Tag_failure_mode table it stopped working. I also made many other
changes, so I can't tell what I did to break it.
Any tips on how to restructure or set stuff up to make this as smooth
as possible?
On 29 apr, 18:43, John W. Vinson <jvinson@STOP_SPAM.WysardOfInfo.com>
wrote:
[quoted text clipped - 23 lines]
