NT607/8? Wizard creation

[terryd]

Hi Bruce
I used the wizard to create an application using the attached dct and small demo tps tables.
If you access the beneficiary history menu choice and select change for any record and then just save on the form the error  message BeneficiaryID: Must be in Table Beneficiary appears.
The link must be there because when you arrive in the form the Beneficiary name appears in the entry field. I have also checked the tps files and they appear to be correct.

[Bruce]

you forgot to attach the files.

cheers
Bruce

[terryd]

Doh!!!

[attachment deleted by admin]

[terryd]

Hi Bruce
Any feedback yet?

[Bruce]

yeah.

You have BeneficaryHistory linked to the Beneficiary table.
Beneficiary has a ID field - but not a (unique) description field. And importantly no (single component) description field key.

So, the wizard has been a little too clever, and not clever enough. UpdateBeneficiaryHistory procedure, BENH:BeneficiaryID field, Lookup Settings - "use Description instead of value" is on - and it should be off. You can obviously change that in the app.

Cheers
Bruce

[terryd]

Thanks
I'll go through my dictionaries and update.
I have had this issue on and off for a while in NT5 as well
So does this mean that if (for example) I have a surname and first name I need to create a composite field with surname + firstname + ID as the unique description field created from the 3 individual fields which will be my unique description field and key

[Bruce]

So the "description in place of value" works if
a) there's a single-component description field
b) which is (preferably) unique
c) there's a single-component key on this field.

Of course this may be the round-about way of solving the problem - if names are not unique (and they're not) then the whole description-instead-of-value thing becomes somewhat moot.