Lookup Behavior When Lookup Table is Empty

Lookup Behavior When Lookup Table is Empty

Post by CR » Sat, 01 Dec 2001 00:38:56

I have a simple lookup that looks up a name based on a code -- very typical.

However, if the table I'm looking at has zero rows, then the lookup returns
the value of the CODE instead of returning nothing.  Why is that?  Can this
be avoided somehow?



1. Lookup Tables to Lookup Tables

I am on a job converting an Oracle database to SQL Server.  We are making
some changes to the data model.  The database includes about 30 lookup
tables which supply necessary data choices to the main table.  In several
cases, there are lookup tables which, in turn, supply data to fields in the
lookup tables.  I haven't come across this before and wherever the
secondary lookup tables consist of only a few choices am recommending to
the client that they eliminate the secondary lookup table and use a
constraint instead on the field in the primary lookup table.  

Are lookup tables to lookup tables standard industry practice?  (My
instinct tells me no but I thought I'd check...)

Donna S.

(Remove no-spam from address before replying!)

2. ComboBox problem

3. Multiple Lookups to the Same Lookup Table

4. Remote database questions (NFS shared access, RServ)

5. DTS, Lookups--Using a lookup in a DTS transform

6. Very strange DTS Lookup behavior

7. is it possible to lookup a field value, based on a lookup that is based on another lookup, in a repeating field?

8. Table Lookup - Updating all records in table

9. lookup tables prevent opening data table

10. Dynamically Updating Table Lookup CTRL-SPACE tables

11. Help -- matching data in lookup table, writing to target table