Re: I have read tons of theory...but still...one question

"Kostas" <noemail_at_noemail.net> wrote in message news:10n0d0ma8jb3ab6_at_corp.supernews.com...
> >
> > I'd like to strongly suggest that mispellings are a user interface issue
> > and
> > NOT a database issue. I think there's value in keeping those two groups
> > of
> > issues separate. That's not to say your choice is the wrong one, but
it
> > ain't database theory that's going to address that.
>
> What you say makes good sense and further clarifies another ambiguous
issue
> for me.
> Thank you.
>
> > BTW, there are ways to design the UI so that its dropdown list is built
> > from all the valid (and correctly spelled) values.
>
> Sort of like MS Access' lookup tables? But if so isn't the database in
this
> case doing internally what I was doing externally by explicitly specifying
> the lookup table?

Since you mentioned Access specifically, there is also the field validation rule
that you can set to limit the values that can be entered. If you're not concerned
with the list being maintainable by the user it makes some sense to eliminate
a table and thus, somewhere down the line, a Join. Received on Sat Oct 16 2004 - 02:04:56 CEST