Thin Client and Treeview

[Martin Kaschke]

Gentlemen,

I am currently working on a project that I have written a thick client for
(VB6). We are about to introduce a new feature which we will develop for
the thick client, but also for the intranet.
The screen will be similar to Windows Explorer, in that it will have a left
and a right treeview. The user will select items from the right to drag
and drop onto the left. The data for the treeviews will be large (10,000+
items),we will be paging about 1000 items in each treeview in unbound mode.
I know we can simulate(through code) a treeview control with the MSFlexgrid
control.

Here are my questions:
Which control (treeview, flexgrid or other) would be the easiest to use for
BOTH the thick, and thin clients? Would using the treeview or grid for the
thin client cause complications?

Which would be the fastest control? Any suggestions for improving data loading
speed?

Thanks a million,

Martin.Kaschke@Cigna.com

[RDJ]

"Martin Kaschke" <Martin.Kaschke@cigna.com> wrote:
>
>Gentlemen,
>
>I am currently working on a project that I have written a thick client for
>(VB6). We are about to introduce a new feature which we will develop for
>the thick client, but also for the intranet.
>The screen will be similar to Windows Explorer, in that it will have a left
>and a right treeview. The user will select items from the right to drag
>and drop onto the left. The data for the treeviews will be large (10,000+
>items),we will be paging about 1000 items in each treeview in unbound mode.
> I know we can simulate(through code) a treeview control with the MSFlexgrid
>control.
>
>Here are my questions:
>Which control (treeview, flexgrid or other) would be the easiest to use
for
>BOTH the thick, and thin clients? Would using the treeview or grid for
the
>thin client cause complications?
>
>Which would be the fastest control? Any suggestions for improving data
loading
>speed?
>
>Thanks a million,
>
>Martin.Kaschke@Cigna.com

Martin,
Loading this much data into a client will never result in a thin client.
It's not only the code that bloats...
Can you group the data in higher levels to make the amount of data sent between
the client and server smaller ??

Robert de Jong
Stepping Stone Consultants

[Martin Kaschke]

"RDJ" <rjon@step-stone.com> wrote:
>
>"Martin Kaschke" <Martin.Kaschke@cigna.com> wrote:
>>
>>Gentlemen,
>>
>>I am currently working on a project that I have written a thick client
for
>>(VB6). We are about to introduce a new feature which we will develop for
>>the thick client, but also for the intranet.
>>The screen will be similar to Windows Explorer, in that it will have a
left
>>and a right treeview. The user will select items from the right to drag
>>and drop onto the left. The data for the treeviews will be large (10,000+
>>items),we will be paging about 1000 items in each treeview in unbound mode.
>> I know we can simulate(through code) a treeview control with the MSFlexgrid
>>control.
>>
>>Here are my questions:
>>Which control (treeview, flexgrid or other) would be the easiest to use
>for
>>BOTH the thick, and thin clients? Would using the treeview or grid for
>the
>>thin client cause complications?
>>
>>Which would be the fastest control? Any suggestions for improving data
>loading
>>speed?
>>
>>Thanks a million,
>>
>>Martin.Kaschke@Cigna.com
>
>Martin,
>Loading this much data into a client will never result in a thin client.
>It's not only the code that bloats...
>Can you group the data in higher levels to make the amount of data sent
between
>the client and server smaller ??
>
>Robert de Jong
>Stepping Stone Consultants

Yes, while we already have cut down the data size, we would like to cut it
down some more, but won't be able to reduce it too much. Which control would
you recommend using? Which will be the fastest for what we want to do?

Thanks,

Martin Kaschke

[RDJ]

Martin,
I have used this approach in a view client / server projects
Investigate the number of levels and how often the data is changed.

If you have view levels concider a listbox for each level and use the value
of the listbox to narrow down the search on the data.
I use a "get data" button instead of the events of the listbox to limit unwanted
roundtrips to the server.

Or...
If the data is static, why not load it on the client side on a daily basis.
With ADO this should be not so hard to do.
Than your queries will ron on the client side and there is no network IO
but once a day.

Robert de Jong