Re: Beginner's DB Design Question

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

1. Yes, enforced relationships are an integral part of the database
relational model and are crucial to protecting the integrity of the data, and
is something a developer would do as a mater of course when setting up a
database. The point being made on the MVPS site is that using the lookup
field wizard is that it creates superfluous relationships and indexes behind
the scenes. We are talking her about actual relationship objects, not
conceptual relationships between entity types.

2. No, you can still implement the design and the functionality as I
described it while having used the lookup field wizard. The database will
work and the day-to-day user will not see any difference provided the
developer has designed it in such a way that the user interfaces with the
data via customized forms and reports, and is not given access to tables
(including the result tables of queries) in raw datasheet view, but the
drawbacks explained on the MVPS site will be present.

Ken Sheridan
Stafford, England

Stephen wrote:
Firstly don't use the so called 'lookup wizard' for a columns data type
when
[quoted text clipped - 11 lines]
unsuitable
as keys.

Wow - thank you Ken. I really appreciate all the effort you went
through to help me with this. This issue seemed like a relatively simple
one - I didn't realize how much of this would rely on coding to make it
work.

I will do what I can to integrate your suggestions and see if I can make
this work.

Incidentally, I looked at the link you provided on the reasons why not
to use a lookup field. Some of them have merit, and I will definitely take
them into consideration in the future, but I was wondering if you could
elaborate on a couple of points:

1. Even if I didn't use lookup fields, I would still need to setup the
appropriate relationships, would I not? I would think so, but number 3 on
that list seems to suggest that this shouldn't be the case.

2. Do the suggestions you made require that there be no lookup fields in
place? Or would that not make a difference in implementing your
suggestions?

Stephen

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-gettingstarted/200906/1

.

Relevant Pages

  • Re: Database Model - Class, objects and interaction
    ... I was just proving stored procedures can call views. ... stuff like security and logging. ... So given 100,000 users, you would create database accounts for each? ... Part of our system's integrity was its reliability, and reliability is often assisted by simplicity. ...
    (comp.object)
  • Re: ODB (Cache?) vs ORM
    ... This is common and accepted database knowledge. ... > other way is error-prone, thus virtually guaranteed to break integrity, producing ... > is multiple orders of magnitude more powerful than procedural optimization. ...
    (comp.lang.java.databases)
  • Re: Where to do Data Validation?
    ... application level (while also having integrity constraints in the ... database) whereas other articles mention that data validation should ... Define 'controlled environment'. ...
    (comp.databases.oracle.misc)
  • Re: update/append query
    ... controlling space there is the possibility of the data ... integrity being broken. ... try to re-import the data to the database you'll get an error. ... Foreign Key to another table - Excel won't be able to enforce data ...
    (microsoft.public.access.queries)
  • Re: NTDS cannot be found, need help
    ... Start the Server in Ad Restore Mode ... To perform an integrity check. ... Delete the database log files from the Winnt/Ntds folder. ... If I try to repair, recover, ...
    (microsoft.public.win2000.active_directory)