Display Description instead of Value

[Thys]

Hi,

On my Location update form, I have a lookup to the Country table. When I have "Display Description instead of Value" switched on in the Country id field on the Location form, it shows the Country name - but when it saves SQL complains that the Country id was not found. When it's switched off (thus the Country id is shown in the Location form and not the Country name), then SQL doesn't complain.

In general for lookup fields, do I need to have a separate field for the lookup description? In a desktop app this will definitely be needed. But why the option then of "Display Description instead of Value"?

Thanks,
Thys

[bijan]

Hi Thys,

Can you show us your Lookup settings tab. I am doing this in a form and a browse(drop down) and it works fine. I am using tps.

Bijan

[Bruce]

if you are doing "display description instead of value" then your lookup table needs a single component key on the description field.
(of course it needs a single-component key on the value field as well.)

cheers
Bruce

[Thys]

Hi Bruce.

Back from leave now. Just installed NT 9.12.

I'm doing a lookup from the Location form to the Country browse. Both tables have a column GUID which is CHAR(16) in SQL as a single-component PK. Attached is a doc with the screenshots, also showing the SQL error.

Thanks,
Thys

[Bruce]

>> if you are doing "display description instead of value" then your lookup table needs a single component key on the description field.
(of course it needs a single-component key on the value field as well.)

Is there a (preferably unique), single component key, on COU:Name?

cheers
Bruce

[Thys]

No, I don't have a key on the description value. I'll add the key to try it.

Thanks