Treeview Limitations

[Scott]

Hi everyone!

My Access app. uses the ActiveX Treeview control to show a hierarchal
structure of records.

Each record has a name and a "parent" along with some other attibutes.
For example:

Item Parent
------------------
Car TOP LEVEL
Engine Car
Wheels Car
Doors Car
Valves Engine
Dipstick Engine
Tyres Wheels
Hinges Door
Handle Door
Screws Hinges

For clarity, I can safely assume that each item is unique and that any
Item can in turn be a parent. I have not imposed any limit on the
number of levels.

For example, the above table might render as follows (apoligies for the
poor ASCII art!):

TOP LEVEL
+Car
.....+Engine
.........-Valves
.........-Dipstick
.....+Doors
.........-Handles
.....+Hinges
.........-Screws
.....+Wheels
.........-Tyres

You get the idea.

It seems to work fine, typically rendering a few thousand records in a
matter of seconds.

The question is, I'm looking to apply this same idea to a dataset of
10's of thousands (probably 40,000). Is this going to be possible? Can
Treeview only handle so much? Early testing seems to indicate that
Access just gives up and crashes.

So I guess i'm asking if anyone has any ideas of how this could be
achieved using a smarter method?
I personally don't really understand mcuh about the Treeview control, I
treat it much like a magic black-box that until recently did it's job
pretty well!

Thanks in advance!
Scott

[Tom van Stiphout]

On 30 Sep 2004 06:58:13 -0700, "Scott" <sm*******@gmai l.com> wrote:

You could always use a 3rd party treeview control if you run into
"limitation s" with Microsoft's. I have had good experience with the
one from Infragistics, albeit in a VB6 environment.

-Tom.

Hi everyone!

My Access app. uses the ActiveX Treeview control to show a hierarchal
structure of records.

Each record has a name and a "parent" along with some other attibutes.
For example:

Item Parent
------------------
Car TOP LEVEL
Engine Car
Wheels Car
Doors Car
Valves Engine
Dipstick Engine
Tyres Wheels
Hinges Door
Handle Door
Screws Hinges

For clarity, I can safely assume that each item is unique and that any
Item can in turn be a parent. I have not imposed any limit on the
number of levels.

For example, the above table might render as follows (apoligies for the
poor ASCII art!):

TOP LEVEL
+Car
....+Engine
........-Valves
........-Dipstick
....+Doors
........-Handles
....+Hinges
........-Screws
....+Wheels
........-Tyres

You get the idea.

It seems to work fine, typically rendering a few thousand records in a
matter of seconds.

The question is, I'm looking to apply this same idea to a dataset of
10's of thousands (probably 40,000). Is this going to be possible? Can
Treeview only handle so much? Early testing seems to indicate that
Access just gives up and crashes.

So I guess i'm asking if anyone has any ideas of how this could be
achieved using a smarter method?
I personally don't really understand mcuh about the Treeview control, I
treat it much like a magic black-box that until recently did it's job
pretty well!

Thanks in advance!
Scott