Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
ListBox show Elements but not .F. when nothing to be sho
Message
From
06/06/2018 17:43:11
Walter Meester
HoogkarspelNetherlands
 
 
To
06/06/2018 08:41:06
Cetin Basoz
Engineerica Inc.
Izmir, Turkey
General information
Forum:
Visual FoxPro
Category:
Object Oriented Programming
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 10
Miscellaneous
Thread ID:
01660530
Message ID:
01660612
Views:
63
>Yes it works for me wonderfully well and cursors are the way to go to populate comboboxes in scalable applications.

I disagree strongly.

>You are just making up unrealistic excuses not to use cursors (sys(1104) for example). You are not filling up the arrays with constants hard coded, do you? If you do then hands down, forget I even said cursor.

There is nothing unrealistic about using a caching object in another data session to populate and refresh combo boxes.

And there is nothing unrealistic about using sys(1104) affecting performance. They are real life scenarios. Sys(1104) is flushing every cursor to disk (temp folder). In the process of doing so, the virusscanner kicks in and wants to scan every cursor. I had several clients reporting slowness in our application and after weeks we came to the conclusion the SYS(1104) in combination with virus scanners was the problem. I would never have found the problem without the help of SET COVERAGE TO which identified a case where it took 15 seconds to do a sys(1104).

You fail me to give a good reason to use cursors for comboboxes and debunk mine with slam dunks. Cetin, it is you who has to think better on what you're proposing.
Again. If it is working for you, fine, but the facts are very clear that cursors populating comboboxes are more problematic than arrays.

Walter,
Previous
Reply
Map
View

Click here to load this message in the networking platform