Why do my value lists that are comprised of two fields in the same table (ID and Name- sorted by the first) only show the first value in IWP? They work in Pro. When I change the sort to the second, things get weird. The first field is the unique key- the name may be used more than once. My users need to see the names to choose. I'm using Server Adv. on Windows 2000. Thanks!

Hi Anna

IWP is a difficult beast to tame.

Second field won't show in either list, menu, check box or radio buttons !

I use a calculated field to show 2 field's at once.

But if you calculate an id field with a name, then you have to add even more steps to strip out the name from the id field. All Anna wants is the id field, the name appears to make it user friendly. So how do we accomplish user friendliness without hours of excess programming?

Here's how I solved this under a tight time constraint (not the most elegant solution but it works).

Define two fields in the local file, ID and Name. Define the value list to use just the name field from the other file. Put the name field on the layout and allow the user to selected from the value List.

Define a relationship between the two Name fields in the two files. In the local file, set the ID field to do an Auto-Enter lookup based on that relationship and grabbing the ID from the second file.

Since the Name can change in the second file, a method is needed to refresh the Name when editing the record. I use a script that's executed when I edit the record, it does a Set Field (a second relationship is needed between the two ID fields).

Clear?

Clear as frog guts. Actually, it does make sense. But the problem is, what if you have two people with the same name?