Odd Behaviour of value list

[Mark Appleby]

I have found an oddity when working with my value lists. When entering data everyting is working fine. but when I am in find mode one of my lists is not working at all?!? Can this be explained? I can see no reason why this is happening.

[Fitch]

When the value list is based on a relationship, it won't work in Find mode unless the relationship is based on a global field. This is because only global fields retain their data in Find mode.

[Mark Appleby]

The funny thing is that it works on other fields on the same screen

[Fitch]

But the other fields are using different value lists... right? Look at your value list and see if its definition is based on a relationship.

[Chuck]

If Tom is correct, and he probably is, you can work around the problem by creating another value list based on a global field. Before you enter find mode, populate the global field with the contents of the value list using the ValueListItems function.

Set Field [ gValueList, ValueListItems( DBName, ValueListName ) ]

Chuck

[Mark Appleby]

The departments is using an ordinary value list while the catagories value list is based on the value entered into the departments field. As far as I can see now the problem is that sub catagory is based on a list that is based on a calculated field. Possibly I will have to change that. By using the above method I will have to start my find and then start a script, which is a little clunky in this situation.

[Mark Appleby]

I fixed it,

The problem was that the relationship that the field was looking up was from a calculated field. The answer was to change the way I had my relationships. The find now works exactly as I wanted. The relationships work!