Re: Not in List Event Error
- From: "AccessVandal via AccessMonster.com" <u18947@uwe>
- Date: Wed, 26 Nov 2008 03:29:55 GMT
Well, I’ll leave it to you to do what ever you want to do with your database.
I would suggest you read up more on RI before you accuse someone. I’m not
saying you can’t have one to many with RI. As according to the details you
have given, it’s a one to one relationship not possible to have a one to many.
Edward wrote:
With all respect, that is incorrect.
RI simply prevents you from deleting the data from a parent table when there
are related records in child tables. The cascade update is simply a smaller
override that allows for automatic refreshing of the child tables without
having to systematically refreshing each field where the reference is found.
Cascade delete overrides the safeties and allows for the deletions of the
child tables' records first before removing the primary record in the parent
table.
In reality, one to one relationships are rare, but they do exist. Many to
many are almost non-existent, and I think IF you get a many-to-many it is
probably because of bad database design. I think the same about one-to-one
relationships UNLESS there are special circumstances where they are needed.
In all of my years of programming, only one program required tables based on
one-to-one relationships. If the database is normalized correctly, the most
common WILL be the one to many relationships. I know because I've been
using this structure for years, and I teach this at the college level. I'm
one of those who actually programs in fourth normal form and sometimes
fifth, depending on the way that the table structure is needed.
Like I said before, I have been updating records in a one-to-many
relationship for years without incident, which is the nomal way of
programming. This same code works fine with unbound tables and to some
degree with the bound table, but it is simply going to another record, which
it shouldn't. I am now leaning toward a corrupt table, which I've seen
Access do before.
In the future, I would appreciate it if you would please refrain from
writing as an expert if you truly are not aware of correct data structure.
While I appreciate your enthusiam to offer assistance, your advice for the
RI is absolutely incorrect on the basis of a one-to-one relationship, and
had I been a programming novice, your advice would have had me chasing down
trails that were incorrect. If your table structures are one-to-one, then
may I suggest that you revist them and evalutate whether or not they have
been normalized correctly.
If you want to maintain RI, you must use one to one relationship. You can't[quoted text clipped - 35 lines]
use one to many. To maintain RI, a child record cannot be an orphan. It
both bound and unbound forms has the underlying recordset pulling
from tbl_cities.
--
Please Rate the posting if helps you
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-formscoding/200811/1
.
- Follow-Ups:
- Re: Not in List Event Error
- From: Edward
- Re: Not in List Event Error
- References:
- Not in List Event Error
- From: Edward
- Re: Not in List Event Error
- From: Keith Wilby
- Re: Not in List Event Error
- From: Edward
- Re: Not in List Event Error
- From: AccessVandal via AccessMonster.com
- Re: Not in List Event Error
- From: Edward
- Re: Not in List Event Error
- From: AccessVandal via AccessMonster.com
- Re: Not in List Event Error
- From: Edward
- Re: Not in List Event Error
- From: AccessVandal via AccessMonster.com
- Re: Not in List Event Error
- From: Edward
- Not in List Event Error
- Prev by Date: Re: Access 2007 - Recordsource & Subform
- Next by Date: Re: Why my dev box shows flat field borders; TS shows chiseled?
- Previous by thread: Re: Not in List Event Error
- Next by thread: Re: Not in List Event Error
- Index(es):
Relevant Pages
|