Alex Thurgood wrote:
True, and it does save time on form building, but on queries using SQL
it's one PITA having to type in so much, with the risk of mistyping or
having to put everything in quotes (OK, most CLI shells have tab
completion if the db supports that feature, so maybe I'm being a bit
excessive).
............................snip
Yes, I tend to agree with him now, although that's because I've had to
make do with Base's shortcomings, to the point where I do nearly
everything in SQL. If I look back to when I was a complete beginner,
I'll willingly admit that is was nice to have GUI features that did
all that ground work for you. This was, and still is the case, with db
tools like FMPro, or Lotus Approach or even the older Borland tools (I
can't speak for Access, having never used it to build anything).
............................snip
I must admit to being a bit of a stickler here - I much prefer to use
lookup lists, but then that is how I learnt from my elders :-) Keep
everything nice and separate, although I can see your point,
especially where the number of distinct values is small, but having
said that, I've created lookup lists for stuff that only had 5
different possible values, so I'm probably too stuck in my own mould
to change now. I've tried using ENUM fields in the past, but here
again, it just doesn't cut the mustard when you've got a lot of stuff
to list, or when you've got to update the lists on a frequent basis.
Well, so much for my ramblings, I'm not convinced that they'll have
brought you any further along your road :-)
Quite to the contrary actually, it is much help and I must admit yours
and Marc's rapid replies have me starting to reconsider already.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
