Re: Denormalizing for form only
- From: "Amy Blankenship" <Amy_nospam@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 10 May 2008 09:19:11 -0500
"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.
.
- Follow-Ups:
- Re: Denormalizing for form only
- From: Jeff Boyce
- Re: Denormalizing for form only
- From: Bob Quintal
- Re: Denormalizing for form only
- References:
- Denormalizing for form only
- From: Amy Blankenship
- Re: Denormalizing for form only
- From: Jeff Boyce
- Denormalizing for form only
- Prev by Date: Re: help with coding a form
- Next by Date: Re: How to open OS window from a form
- Previous by thread: Re: Denormalizing for form only
- Next by thread: Re: Denormalizing for form only
- Index(es):
Relevant Pages
|