|
Originally Posted by AKAJohnDoe
|
I'm not sure I quite understand.
I have a number of ListPro lists that I've created that I did not include a category field in their definitions.
If I'm not mistaken, in ListPro terminology, while it is possible to create a field with the name CATEGORY, that category is actually a field type. And therefore, any field with the type of category automatically tracks the values that have been input into the records for that field and dynamically maintains a drop-down box of those categories, or types.
|
For me, an ole time dBase programmer, using ListPro terminology is awarkward, as it is not true database terminology. They call the values in a typical drop down box "category values". Really they are drop down values.
Let's see if I can better explain it. In my dropdown that is self propagating from data values entered, rather than previous values being shown in alpha order, they are apparently shown in order entered. For example, the field has values of "banana", "apple", "pear", "orange" and "plum". Rather than listing them in the drop down as, "apple", "banana", "orange", "pear" and "plum", it lists them just as first typed.
It has this problem only with character fields. If it is a numeric field, it automatically lists them in numeric order.
As an update, since I closed the file last night and just reopened it today, it now lists them in alpha order. So apparently it requires a file close to have the alpha fields drop down values properly sorted. This is a program bug.
Thanks for trying to help. Maybe the makers of ListPro will fix this.
Cheers,
Dobermann