Treeview control - duplicate keys

[Jenifer.Austin]

MS Access 2000

I have created a large treeview control based on lists of parts. The
nodekey for a part consists of a character followed by the parent
part's index. Some of these parts (e.g., screws) will show up many
times in the same relative position in the treeview. How can I avoid
getting duplicate key error messages? Here's a simplified version of
my treeview control:

Widget 1
Frob a
Frob b
Screw 1
Screw 2
Widget 2
Frob b
Screw 1
Screw 2
Widget 3
Frob a
Frob c
Screw 2
Screw 3

I have tried incrementing the character in front of the part's index
each time I call the recursive subroutine to create a new branch, and
it seems to work, but only to the second level of parts (in my sample
above, the "Frobs" are fine, but not the screws).

[Tom van Stiphout]

On Mon, 11 Jun 2007 19:03:53 -0700, Je************@comcast.net wrote:

I have dealt with the same issue by assigning the key as the
concatenation of the various levels it is in. I used a
querystring-like format, e.g.:
Widget 1: w=1
Widget 1 - Frob a: w=1&f=a
Widget 1 - Frob b - Screw 1: w=1&f=b&s=1

Then write a few functions to pick apart the "querystring" (I used a
scripting.dictionary object) and test if a certain element exists.
A key like this comes in very handy when for example the user clicks
on a Screw 1 object: you immediately know what this object is a part
of, without walking the tree.

-Tom.

>MS Access 2000

I have created a large treeview control based on lists of parts. The
nodekey for a part consists of a character followed by the parent
part's index. Some of these parts (e.g., screws) will show up many
times in the same relative position in the treeview. How can I avoid
getting duplicate key error messages? Here's a simplified version of
my treeview control:

Widget 1
Frob a
Frob b
Screw 1
Screw 2
Widget 2
Frob b
Screw 1
Screw 2
Widget 3
Frob a
Frob c
Screw 2
Screw 3

I have tried incrementing the character in front of the part's index
each time I call the recursive subroutine to create a new branch, and
it seems to work, but only to the second level of parts (in my sample
above, the "Frobs" are fine, but not the screws).

[Jenifer.Austin]

I was afraid you were going to suggest this. I have been trying to do
this, with mixed results -- but I recently found that some of the
parts I'd been given had circular references! Thanks for the advice,
I'll slog through it and once I get the data cleaned up, hopefully
this will work.

Regards,

Jenifer
On Jun 12, 12:44 am, Tom van Stiphout <[e-mail]:

On Mon, 11 Jun 2007 19:03:53 -0700, [e-mail] wrote:

I have dealt with the same issue by assigning the key as the
concatenation of the various levels it is in. I used a
querystring-like format, e.g.:
Widget 1: w=1
Widget 1 - Frob a: w=1&f=a
Widget 1 - Frob b - Screw 1: w=1&f=b&s=1

Then write a few functions to pick apart the "querystring" (I used a
scripting.dictionary object) and test if a certain element exists.
A key like this comes in very handy when for example the user clicks
on a Screw 1 object: you immediately know what this object is a part
of, without walking the tree.

-Tom.

MS Access 2000

I have created a large treeview control based on lists of parts. The
nodekey for a part consists of a character followed by the parent
part's index. Some of these parts (e.g., screws) will show up many
times in the same relative position in the treeview. How can I avoid
getting duplicate key error messages? Here's a simplified version of....