No Data in Drop-Down Lists

[Deb]

I have a table with 10 drop down lists (information supplied by 10 separate
drop-down tables). Most of the drop-downs work perfectly. Two, however, do
not appear to be working the way I'd like them to.

One displays the information in the second column, the first column contains
the code for the description displayed in the second column. The problem is
that the codes in the first column are not displayed, although I can actually
see the column itself, just nothing in it.

A second drop-down has three columns but none of the information is
displayed. If you click (select an invisible item from the list) it displays
the information in the new table, but there is no way of knowing what you're
selecting.

Please HELP!!

 

[Arvin Meyer MVP]

In the property sheet for those 2 combo boxes, look at the column count and
column width properties. One or both may need adjusting.

 

[Duane Hookom]

It sounds like you are using Lookup fields in your table design. If so,
consider reading this http://www.mvps.org/access/lookupfields.htm. Most of us
that have been around for a while never use lookup fields. We create forms
with combo boxes for user interaction.

If you have questions about the combo boxes, please come back with all or
the significant properties such as:
Control Source:
Row Source:
Column Count:
Bound Column:
Column Widths:

 

[Deb]

Okay - here is the requested information.

Control Source: Not offered from table design view
Row Source: SELECT tlu_TransactionCodes.ID,
tlu_TransactionCodes.TransactionCode,
tlu_TransactionCodes.TransactionDescription
FROM tlu_Transaction Codes ORDER BY [TransactionCode]"
Column Count: 3
Bound Column: 1
Column Widths: 0", 0.6875", 1.3438"

I went to "The Evils of Lookup Fields in Tables" and decided my total
approach is probably wrong. I've set the main table (tbl_Inventory) up with
lookup fields right in the table. Should that be done at the form level?

I'm also having problems with using a combo box to lookup information to
fill in a form. It does the same thing that was being done in the table. I
can actually see columns (3 columns should be visible from the combo box),
but the information is not visible.

 

[Duane Hookom]

Do you really have the double-quote at the end of
SELECT tlu_TransactionCodes.ID,
tlu_TransactionCodes.TransactionCode,
tlu_TransactionCodes.TransactionDescription
FROM tlu_Transaction Codes ORDER BY [TransactionCode]"

Can you take the above SQL and create a query from it and see the records?

IMO, this should be used on forms, not in table design. You can set
relationships as necessary but I wouldn't define lookups in the table.
--
Duane Hookom
Microsoft Access MVP

Okay - here is the requested information.

Control Source: Not offered from table design view
Row Source: SELECT tlu_TransactionCodes.ID,
tlu_TransactionCodes.TransactionCode,
tlu_TransactionCodes.TransactionDescription
FROM tlu_Transaction Codes ORDER BY [TransactionCode]"
Column Count: 3
Bound Column: 1
Column Widths: 0", 0.6875", 1.3438"

I went to "The Evils of Lookup Fields in Tables" and decided my total
approach is probably wrong. I've set the main table (tbl_Inventory) up with
lookup fields right in the table. Should that be done at the form level?

I'm also having problems with using a combo box to lookup information to
fill in a form. It does the same thing that was being done in the table. I
can actually see columns (3 columns should be visible from the combo box),
but the information is not visible.

It sounds like you are using Lookup fields in your table design. If so,
consider reading this http://www.mvps.org/access/lookupfields.htm. Most of us
that have been around for a while never use lookup fields. We create forms
with combo boxes for user interaction.

If you have questions about the combo boxes, please come back with all or
the significant properties such as:
Control Source:
Row Source:
Column Count:
Bound Column:
Column Widths:

 

[Deb]

Hi Duane:

I keep trying to reply, but get error messages saying that I can't post.
I've already tried to send posts back three times -- very frustrating.

No, there is no double-quote at the end of the Select Statement. It has a
semicolon (I mistyped).

Okay, if I don't set the table up using the Lookup Wizard for the underlying
tables, do I format the table fields like the the same as the format of the
data being stored from the lookup table? I'm fairly new at this (as you can
tell) - and appreciate any and all help and suggestions.

Thank you, Deb

Do you really have the double-quote at the end of
SELECT tlu_TransactionCodes.ID,
tlu_TransactionCodes.TransactionCode,
tlu_TransactionCodes.TransactionDescription
FROM tlu_Transaction Codes ORDER BY [TransactionCode]"

Can you take the above SQL and create a query from it and see the records?

IMO, this should be used on forms, not in table design. You can set
relationships as necessary but I wouldn't define lookups in the table.
--
Duane Hookom
Microsoft Access MVP

Okay - here is the requested information.

Control Source: Not offered from table design view
Row Source: SELECT tlu_TransactionCodes.ID,
tlu_TransactionCodes.TransactionCode,
tlu_TransactionCodes.TransactionDescription
FROM tlu_Transaction Codes ORDER BY [TransactionCode]"
Column Count: 3
Bound Column: 1
Column Widths: 0", 0.6875", 1.3438"

I went to "The Evils of Lookup Fields in Tables" and decided my total
approach is probably wrong. I've set the main table (tbl_Inventory) up with
lookup fields right in the table. Should that be done at the form level?

I'm also having problems with using a combo box to lookup information to
fill in a form. It does the same thing that was being done in the table. I
can actually see columns (3 columns should be visible from the combo box),
but the information is not visible.

It sounds like you are using Lookup fields in your table design. If so,
consider reading this http://www.mvps.org/access/lookupfields.htm. Most of us
that have been around for a while never use lookup fields. We create forms
with combo boxes for user interaction.

If you have questions about the combo boxes, please come back with all or
the significant properties such as:
Control Source:
Row Source:
Column Count:
Bound Column:
Column Widths:

--
Duane Hookom
Microsoft Access MVP


:

I have a table with 10 drop down lists (information supplied by 10 separate
drop-down tables). Most of the drop-downs work perfectly. Two, however, do
not appear to be working the way I'd like them to.

One displays the information in the second column, the first column contains
the code for the description displayed in the second column. The problem is
that the codes in the first column are not displayed, although I can actually
see the column itself, just nothing in it.

A second drop-down has three columns but none of the information is
displayed. If you click (select an invisible item from the list) it displays
the information in the new table, but there is no way of knowing what you're
selecting.

Please HELP!!

 

[Deb]

Many thanks, Linq! (Sorry it has taken so long to reply, left on 5/20 for
family emergency out of state!)

Your advice was dead on! And I have to say, that blasted cat has been
skinning me for a long time now, feels good to be skinning him for a change!

Thanks again!