Slow Pop up list

[Mark Appleby]

I am having a slight problem with a pop up list. It is taking a couple of seconds to dropdown. I can not see why? As there are only about 120 records in it. When you go into the field it takes about 2 seconds to see the dropdown list. Can anyone tell me why?

[danjacoby]

Do you mean there are 120 values in the list? If so (and especially if the list is pulling from the contents of a field), it might take a little while to load all those values.

[JerrySalem]

If the popup is pulling from a field, I think making sure the field is indexed would give you an improvment. Also if the Value List field is a calculation, it should be a stored calc (if that is appropriate for your DB).

[CobaltSky]

A value list cannot be based on a field which is not both stored and indexed.

If you try to create such a value list your will get an error message, and if you proceed anyway, the value list will not work at all.

Since Mark's value list is working, (albeit after a short delay) it is clearly either hard coded or based on an indexed field.

However as Dan says, we really need more information about what it is based on and how etc in order to be able to provide any useful suggestions.

[Mark Appleby]

Thanks for so much Input folks. The field is based on a supplier file.

I have noticed one thing that is interesting though and that is when used on a new file that I am working on this list is instant.

I can forsee a different problem in the future. I was considering using something similar for sales entry which would lookup a database with about 15000 names. If 120 records takes two seconds how long would it take with 15000.

[CobaltSky]

A list which has only 120 entries drawn from a field in a related file should normally display within half a second or so.

In multi-user mode, network overheads can impact this. However the fact that the list is instantaneous when accessed on your new file suggests that there is something amiss in the set-up of the file you are experiencing the problem with.

For example, if the value list is conditional based on a relationship, and the primary key for the relationship includes a summary function that could introduce a delay. There are other possibilities of this kind but, without more information about the way your file is set up they would all be no more than a stab in the dark.

[danjacoby]

Wait a minute!

How many names are in the value list? Is that the 120 names that could eventually be 15,000?

The speed with which the value list opens should have nothing to do with the number of records in the main file, unless the list pulls from a field IN THAT FILE, in which case as more different entries are added to that field things will slow down.

[Mark Appleby]

In Reply to all. The value list in question is based on a single field in another file with 120 records. This I could not see exceeding 200 entries.

The value list is based on Supplier names in my supplier file from my product style file.

The Value list of 15000 records is different and I think after consideration I should have some sort of lookup Layout to find the customer names as when I tried the value list approach it is difficult to find the information in question, particularly because the people who will use this feature will not be familiar with use of the keyboard.

I will have to think about this using a different approach suggestions are welcome.