Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


Is it "bad" to have a Lookup table/query in a table?

Is it "bad" to have a Lookup table/query in a table?

Is it "bad" to have a Lookup table/query in a table?

In my database I have one main table called tblSongs that I use to categorize all sorts of information related to selecting, printing lyrics and chord charts, and tracking history of what got played, where, and when.

In the main table, there's a field called "Tempo" where I have a (I believe it's called) Validation table. It's pretty simple, you get to choose "Slow", "Medium", or "Fast". When I made this db 10 years ago, I guess I thought it made sense (or possible MS Access did this automatically?) to have a lookup query so when I open the table itself I don't see the ID number, but rather the text. I guess this helps when you use the wizard to create a form.

The question I have is, is this "bad" to have that? Does it muck up other stuff somehow?

Sorry for the really general question but as I'm updating and modifying the database I want to make sure I'm not painting myself into a corner, so to speak.



RE: Is it "bad" to have a Lookup table/query in a table?


Thanks buddy. :)



RE: Is it "bad" to have a Lookup table/query in a table?

He-he - good to see.

I don't know why, but I always instinctively ignored MS Access 'lookup' references; I think that I felt that they were a 'built-in' but 'hidden' feature, specific to MS Access.
I always created my own 'lookup' queries, based on simple SQL selects from table data.

Nice to see that I haven't missed out on a super-useful 'feature' (which it's sad to say - I have done many times in the past).



RE: Is it "bad" to have a Lookup table/query in a table?

What's really really useful is when you're using it to look directly at tables.

What makes it "hard" is when you're wanting to perform a query using a validation table, you have to use the ID rather than the text. That's better, actually, but just a smidge harder to edit when you go in to make changes and such.



Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close