Results 1 to 3 of 3
  1. #1
    2 Star Lounger
    Join Date
    Nov 2004
    Location
    London, United Kingdom
    Posts
    152
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Lookup fields in tables (any version)

    I have recently read that it is not a good idea to create lookup fields in tables, and to save them for form design. I can understand this when it comes to lookups that use other tables or queries. Is it however the case when using a value list for a lookup? If so, why?

    Many thanks

    Amanda

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 28 Times in 28 Posts

    Re: Lookup fields in tables (any version)

    I'm not 100% sure, but I would guess that a value list lookup does not generate any noticeable overhead.

  3. #3
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,613
    Thanks
    3
    Thanked 58 Times in 58 Posts

    Re: Lookup fields in tables (any version)

    There are a couple of other reasons to not use them. For one thing, you get unexpected results when you sort on a field that uses a lookup - the sort is done in the order of the underlying field, not the lookup value. Also, in general we don't allow users to work at the table level, only using forms. Thus we choose not to use the lookup since noone looks at the table.
    Wendell

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •