Frank,
I'm in total agreement, but the way that DBI's ctGrid loads its combo is
a little different.
Essentially, you load all the possible data into the ctGrid memory
manager, and then the "drop down" acts like an incremental search. My
clients love it. Once the data is loaded into ctGrid, it's extremely
fast. Heck, on all platforms except Win7+VFP runtime it's extremely fast
in all regards.
I hadn't mentioned it, but I have another DBI OCX that I'm using on
another form, the SKU Editor form, that loads the same list of 23,000
SKUs and it....ready for this?....is slow. Same performance as the ctGrid.
I agree with you that needing to load 23,000 SKUs into a combo is over
the top, and that will be addressed soon with my client, but for now,
why would the performance be so dramatically different just because the
OS changes is my question. (Yeah, I know, at some point you have to get
past the problem and accept a work-around.)
Thanks for grok'ing this!
Mike
> Hi Mike,
>
> loading 23,000 SKUs isn't the problem, but loading them in a combo
> box/drop down list is what the others' comments were about. I believe
> the interface guidelines are that a combo is for a relatively few
> choices (less than 100 or 200 is the maximum I've heard mentioned). You
> can use a grid with an incremental search which will give the end user a
> better experience for that amount of data. I only ever use a combo with
> maximum 10 choices.
>
> Frank.
>
> Frank Cazabon
> Samaan Systems Ltd. - Developing Solutions
> www.SamaanSystems.com
>
> Referrals are important to us.
> If you know of anyone who would benefit from our services, please contact me.
> We would appreciate the opportunity to work with them.
>
>
> On 03/03/2011 03:09 PM, Mike Copeland wrote:
>> Thanks Mike! I'll try that. Hell, I'll try anything.
>>
>> The "WHILE !EOF('temp')" is an old habit that makes it easier for me to
>> read the code and grasp what is going on.
>>
>> As for the 23,000 items...I'm in an odd situation with a client that
>> involves both technical-computer issues and my competency, and political
>> issues with a new co-owner. The new co-owner is, for want of a better
>> term, frothing at the bit to dump my app and me and bring in his "guy."
>>
>> I've approached the fact that having 23,000 SKUs available at all times
>> is way over the top (they could easily get by with 7,000), and the code
>> does run faster with fewer SKUs in the pie, but using that as the
>> solution is going to be used as another brick in the wall in the
>> political situation.
>>
>> And, I have to confess that it just rubs me wrong that my app is running
>> great until Windows 7 becomes an issue. Suddenly I'm thinking like a
>> curmudgeon...."Why can't we all go back to Windows NT?"
>>
>> I'll let you know about the impact from the code tweaks, if any. Thanks
>> again!
>>
>> Mike
>>
>>> On 3/2/2011 3:02 PM, Mike Copeland wrote:
>>> <snipped>
>>>> MESSAGEBOX('Starting to load Grid. Click OK to start...',0+64,'Notice')
>>>> LOCAL ttimestart,ttimeexp
>>>> SELECT sku FROM skus into temp WHERE active=1 order by sku
>>>> SELECT temp
>>>> GO TOP IN temp
>>>>
>>>> ttimestart=seconds()
>>>>
>>>> SCAN WHILE !EOF('temp')
>>>> thisform.ctGrid.addcomboitem(1,temp.sku)
>>>> ENDSCAN
>>> Mike,
>>>
>>> Slight tweaks:
>>>
>>> > MESSAGEBOX('Starting to load Grid. Click OK to
>>> start...',0+64,'Notice')
>>> > LOCAL ttimestart,ttimeexp
>>> > SELECT sku FROM skus into CURSOR temp WHERE active=1 order by sku
>>> > SELECT temp
>>> > LOCATE
>>> >
>>> > ttimestart=seconds()
>>> >
>>> > SCAN
>>> > thisform.ctGrid.addcomboitem(1,temp.sku)
>>> > ENDSCAN
>>>
>>> Not sure if that'll make much difference, but it's known that LOCATE is
>>> quicker than GO TOP. Also, your SCAN loop doesn't need the WHILE !EOF
>>> clause.
>>>
>>> My comment on the design is that I wouldn't do 23,000 items in a combo,
>>> but I guess you can't change that now?
>>>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/4d6ffbd2.4070...@ggisoft.com
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
