Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
.Net 2.0 Slower than Foxpro
Message
From
03/01/2006 07:53:33
Cetin Basoz
Engineerica Inc.
Izmir, Turkey
 
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro and .NET
Environment versions
Visual FoxPro:
VFP 9
OS:
Windows XP
Network:
Windows 2003 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
01080435
Message ID:
01082554
Views:
14
>Actually in our application there are forms which used non-grid approaches
>(TV,LV,listbox,combo etc) and our customers are pushing us hard to make them grid based navigators also. They see it as an upgrade to the particular forms rather than going back to yesterday (and if yesterday is better then there is nothing wrong to be so yesterday).

>
>I am only making fun of myself. Grids can be well done. But IMO - if the the data is limited in scope and a grid navigator is desired - list view seems more appealing. They're cached. The table moves when the slider is moved. Any column can be sorted without an index. Column header pictures!
>
>My 1.8GH box can xBase several hundred records into an LV (sometimes 20 to 30 columns) faster than a grid refresh and NO hour glass. Progamatically setting points of other related "list" objects that are open is quick. Its a node click. LV also offers a hittest for really quick xbase data flows.
>
>Grids, OTOH, are snap to. If related grids are open - and a pointer is changed - to visually show the pointer change on related grids requires a "go to" or "seek" on each cursor, a "setfocus" (and in some cases "refresh").
>
>With LV just set the key and its done (we can fire all open LVs through the base class methods!). As a navigator - an LV just seems sexier than Grid. I have written some exotic AfterRowColChange methods in my career - loved every little nubble of code! For me and the time being, in most "navigation control" cases "nodeclick" in LV would be difficult to argue against.

Terry,
I wasn't talking of several hundred records but several hundred thousands of records:) Maybe it's me, with LVs I have hourglass vs with grids I don't have it. With activex (not talking just about LV and TV) I've learned it hard that they had undocumented (unless in fineprint that I missed) limits.

"the pointer change on related grids requires a "go to" or "seek" on each cursor, a "setfocus" (and in some cases "refresh")." This is not entirely true.

Anyway it's a matter of choice so nothing to argue.
Cetin
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform