Re: Denormalizing for form only

"Amy Blankenship" <Amy_nospam@xxxxxxxxxxxxxxxxxxxxxx> wrote in
news:ul8gXjqsIHA.552@xxxxxxxxxxxxxxxxxxxx:


"Jeff Boyce" <nonsense@xxxxxxxxxxxx> wrote in message
news:efBDHaisIHA.5832@xxxxxxxxxxxxxxxxxxxxxxx
Amy

Although the Excel-like Thing1, Thing2, Thing3 approach is
familiar to Excel users, as you already know, it isn't necessary
(or desirable) to use this in an Access database.

What I've found quite useful for such one-to-many relationship is
a main form/subform construction.

So your position is to force the client to adapt to how Access
does things, rather than finding a way to force Access to present
information in the way your client finds easiest to work with.
That's interesting, but it doesn't really answer my question. My
preference is to try were possible to do things in a way that my
client prefers.

Amy,

you seem a little frustrated, but you are in error when you say
But there is a reason people keep asking questions like this, and
it is that Access does a much better job of making it easy to
make data entry forms with the structure above than with the
"correct" structure.

That's not the real reason, the truth is that until people are
familiar with the relational model, they tend to think "spread***
on steroids", and build the database based on that presumption.

I'm wondering if there isn't something I've been missing, some
wonderfully simple feature of Access, that makes using normalized
data less painful from a form-building point of view.

Yes, what you've been missing is using a proper subform with
properly defined relations between the tables and queries. Building
proper data input and data editing form/subform sets becomes child's
play once you learn how. The relational structure becomes
transparent to the client.

As to your preference in doing what your client prefers, I say it is
just lack of confidence in asserting that he will prefer it once
he's used to it.

--
Bob Quintal

PA is y I've altered my email address.
** Posted from http://www.teranews.com **
.

Loading