Slow drop-down list ... any solution?

[PatriciaW]

A drop-down list which has a value list with about 20 values takes several seconds to drop down. I've read on the FM site that this can be caused by having multiple windows and/or open files. In this case, there are between 5 and 6 windows. And around 8 files. I've followed the separation model so the UI is in a single file and there are 7 data files.

I cannot reduce the number of windows without hurting functionality ... ditto the files ...

Has anyone been able to improve the performance of drop-down lists? (Drop-down menus are not an option because they do not drop-down when tabbed into ... only when data is entered ... also they allow data other than that in the list.)

[Reed]

Is the value list conditional, based on a relationship?

Do all the windows actually have to be open at the same time?

Even if you're using the separation model, typically you would put all or most of the data into one or two files, and there would be no layouts or windows associated with those files. They would just be opened hidden so the interface file could access the data.

In any case, I've noticed a significant increase in popup list performance in version 8.

[PatriciaW]

Is the value list conditional, based on a relationship?

If I understand you correctly, no ... there is no reference to a table.

Do all the windows actually have to be open at the same time?

At least 3 with an optional additional one when they are updating one of the entities. I've just put in the code to close 2 windows while they are not in use.

Even if you're using the separation model, typically you would put all or most of the data into one or two files, and there would be no layouts or windows associated with those files. They would just be opened hidden so the interface file could access the data.

I have defined the data files as separate data files for each entity. I did this for two reasons: it makes maintenance simpler, and I could not figure out how to combine database definitions without manually defining each table again, which I feared would introduce a lot of errors. The only layouts in the data files are the single one that FM requires and a couple of scripts for converting the data from FM6 to FM7.

In any case, I've noticed a significant increase in popup list performance in version 8.

Unfortunately, I don't think that the user would want to spend the money for an upgrade when they haven't even put FM7 into production. :P

[sbg2]

(Drop-down menus are not an option because they do not drop-down when tabbed into ... only when data is entered ... also they allow data other than that in the list.)

In Windows the drop-down menus do drop when tabbed into (data or no data), I find it odd (but not out of the question) that they wouldn't drop down on a Mac. I think Menu's are less likely to have data other than that in the list as a user can not type in the field. You can also use field validation = Member of Value List .

I think you are SOL as far as slow drop down lists in FM7, I'm in the same boat. The fact that they seem to have "fixed" this in FM8 doesn't leave the greatest taste in my mouth that they have ignored the problem with FM7.

[Vaughan]

"A drop-down list which has a value list with about 20 values takes several seconds to drop down."

This is a known issue with FMP 7: drop-down lists are dead slow.

Download the FMP 8 trial version and see if it's any better.

[PatriciaW]

Interesting ... I downloaded the trial but it is practically unusable because the items in the File menu are all shifted so far right that I have to guess what they are ... there are 3 characters at max visible. Is this a bug that is just in the trial version?

But, it has speeded up the pop-up list performance.

[Sergeant Ron]

FM8 is way better. same speed as FM6.