Treatise on Tree Control 6.0?

[(Pete Cresswell)]

I'm getting nodes into the thing, but when the dust settles, only the root-level
nodes are visible.

I know they're there because .Nodes.Count gives the right number.\

But I don't really understand the significance of the Nodes.Add syntax - I'm
just slavishly plugging in values.
Viz:

---------------------------
Public Sub ClassMembersLoad(ByVal theClassID As Long, ByVal theMaxLevels As
Long)
1000 debugStackPush Me.Name & ": ClassMembersLoad"
1001 On Error GoTo ClassMembersLoad_err

' PURPOSE: Allow the "Classes" subform to load the "ClassMember"
' tree with members of currently selected class
' ACCEPTS: - ClassID of class's members TB loaded.
' - Max levels TB expected for the class in question

1002 Dim thisDB As DAO.Database
Dim myRS As DAO.Recordset
Dim myQuery As DAO.QueryDef
Dim curNode As Node
Dim curChild As String
Dim curParent As String

Dim i As Integer

1009 Me.treClassMembers.Nodes.Clear

1010 Set thisDB = CurDB()

1020 For i = 1 To theMaxLevels
1030 Set myQuery = thisDB.QueryDefs("qryAdminClassMembersLoad")
1031 With myQuery
1032 .Parameters("theClassID") = theClassID
1033 .Parameters("theLevel") = i
On Error Resume Next
myRS.Close
On Error GoTo ClassMembersLoad_err
1035 Set myRS = .OpenRecordset(dbOpenSnapshot, dbForwardOnly)
1039 End With

1040 With myRS
1041 If Not ((.BOF = True) And (.EOF = True)) Then
1042 Do Until .EOF = True
1043 If Val(!ParentClassMemberID & "") = 0 Then
1044 curChild = !ChildName & "-" & !ChildDescription
1045 Set curNode = Me.treClassMembers.Nodes.Add(, , curChild,
curChild)
'1045 Set curNode = Me.treClassMembers.Nodes.Add(, ,
CStr(!ChildClassMemberID), curChild)
1046 Else
1049 curChild = !ChildName & "-" & !ChildDescription
1050 curParent = !ParentName & "-" & !ParentDescription
1051 Set curNode = Me.treClassMembers.Nodes.Add(curParent,
tvwChild, curChild, curChild)
'1051 Set curNode = Me.treClassMembers.Nodes.Add(curParent,
tvwChild, !ChildClassMemberID, curChild)
' Set curNode = trTable.Nodes.Add(CStr(recLevel2("level1")),
tvwChild, CStr(recLevel2("NodeName")) & "(" & CStr(recLevel2("NodeName")) & ")",
recLevel2("level2"))
1052 End If
1053 .MoveNext
1054 Loop
1055 End If
1059 End With
1999 Next i

'With Me.treClassMembers.Nodes
' For i = 1 To .Count
' Debug.Print .Item(i)
' Next i
'End With
ClassMembersLoad_xit:
debugStackPop
On Error Resume Next
Set myQuery = Nothing
myRS.Close
Set myRS = Nothing
Set thisDB = Nothing
Exit Sub

ClassMembersLoad_err:
bugAlert True, ""
Resume ClassMembersLoad_xit
End Sub
---------------------------

Some time ago Larry Linton pointed me to
http://www.mvps.org/ccrp/controls/ccrpftv6.htm
which works great.

Only problem is that with my current project there is zero chance of registering
an new OCX on a user's machine (corporate security policy).

So I'm back to the plain-vanilla-out-of-the-box control.

Anybody know where to find a decent writeup on the ins and outs of using it.

--
PeteCresswell

[Douglas J. Steele]

The attached, from the VB help file, may be of use to you:

Syntax

object.Add(relative, relationship, key, text, image, selectedimage)

The Add method syntax has these parts:

Part Description
Object Required. An object expression that evaluates to an object in the
Applies To list.
Relative Optional. The index number or key of a pre-existing Node object.
The relationship between the new node and this pre-existing node is found in
the next argument, relationship.
Relationship Optional. Specifies the relative placement of the Node object,
as described in Settings.
Key Optional. A unique string that can be used to retrieve the Node with the
Item method.
Text Optiona. The string that appears in the Node.
Image Optional. The index of an image in an associated ImageList control.
Selectedimage Optional. The index of an image in an associated ImageList
control that is shown when the Node is selected.
Settings

The settings for relationship are:

Constant Value Description
TvwFirst 0 First. The Node is placed before all other nodes at the same
level of the node named in relative.
TvwLast 1 Last. The Node is placed after all other nodes at the same level
of the node named in relative. Any Node added subsequently may be placed
after one added as Last.
TvwNext 2 (Default) Next. The Node is placed after the node named in
relative.
TvwPrevious 3 Previous. The Node is placed before the node named in
relative.
TvwChild 4 Child. The Node becomes a child node of the node named in
relative.
Note If no Node object is named in relative, the new node is placed in the
last position of the top node hierarchy.

Remarks

The Nodes collection is a 1-based collection.

As a Node object is added it is assigned an index number, which is stored in
the Node object's Index property. This value of the newest member is the
value of the Node collection's Count property.

Because the Add method returns a reference to the newly created Node object,
it is most convenient to set properties of the new Node using this
reference. The following example adds several Node objects with identical
properties:

Private Sub CreateNodes()
' Set CheckBoxes property to True to see checked nodes:
TreeView1.CheckBoxes = True
Dim nodX As Node ' Declare the object variable.
Dim i as Integer ' Declare a counter variable.
For i = 1 to 4
Set nodX = TreeView1.Nodes.Add(,,,"Node " & Cstr(i))
' Use the reference to set other properties, such as Bold.
NodX.Bold = True
' Set image property to image 3 in an associated ImageList.
nodX.Checked = True
Next i
End Sub

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(No private e-mails, please)

"(Pete Cresswell)" <x@y.z> wrote in message
news:j2********************************@4ax.com...

I'm getting nodes into the thing, but when the dust settles, only the root-level nodes are visible.

I know they're there because .Nodes.Count gives the right number.\

But I don't really understand the significance of the Nodes.Add syntax - I'm just slavishly plugging in values.
Viz:

---------------------------
Public Sub ClassMembersLoad(ByVal theClassID As Long, ByVal theMaxLevels As Long)
1000 debugStackPush Me.Name & ": ClassMembersLoad"
1001 On Error GoTo ClassMembersLoad_err

' PURPOSE: Allow the "Classes" subform to load the "ClassMember"
' tree with members of currently selected class
' ACCEPTS: - ClassID of class's members TB loaded.
' - Max levels TB expected for the class in question

1002 Dim thisDB As DAO.Database
Dim myRS As DAO.Recordset
Dim myQuery As DAO.QueryDef
Dim curNode As Node
Dim curChild As String
Dim curParent As String

Dim i As Integer

1009 Me.treClassMembers.Nodes.Clear

1010 Set thisDB = CurDB()

1020 For i = 1 To theMaxLevels
1030 Set myQuery = thisDB.QueryDefs("qryAdminClassMembersLoad")
1031 With myQuery
1032 .Parameters("theClassID") = theClassID
1033 .Parameters("theLevel") = i
On Error Resume Next
myRS.Close
On Error GoTo ClassMembersLoad_err
1035 Set myRS = .OpenRecordset(dbOpenSnapshot, dbForwardOnly)
1039 End With

1040 With myRS
1041 If Not ((.BOF = True) And (.EOF = True)) Then
1042 Do Until .EOF = True
1043 If Val(!ParentClassMemberID & "") = 0 Then
1044 curChild = !ChildName & "-" & !ChildDescription
1045 Set curNode = Me.treClassMembers.Nodes.Add(, , curChild, curChild)
'1045 Set curNode = Me.treClassMembers.Nodes.Add(, ,
CStr(!ChildClassMemberID), curChild)
1046 Else
1049 curChild = !ChildName & "-" & !ChildDescription
1050 curParent = !ParentName & "-" & !ParentDescription
1051 Set curNode = Me.treClassMembers.Nodes.Add(curParent,
tvwChild, curChild, curChild)
'1051 Set curNode = Me.treClassMembers.Nodes.Add(curParent,
tvwChild, !ChildClassMemberID, curChild)
' Set curNode = trTable.Nodes.Add(CStr(recLevel2("level1")), tvwChild, CStr(recLevel2("NodeName")) & "(" & CStr(recLevel2("NodeName")) & ")", recLevel2("level2"))
1052 End If
1053 .MoveNext
1054 Loop
1055 End If
1059 End With
1999 Next i

'With Me.treClassMembers.Nodes
' For i = 1 To .Count
' Debug.Print .Item(i)
' Next i
'End With
ClassMembersLoad_xit:
debugStackPop
On Error Resume Next
Set myQuery = Nothing
myRS.Close
Set myRS = Nothing
Set thisDB = Nothing
Exit Sub

ClassMembersLoad_err:
bugAlert True, ""
Resume ClassMembersLoad_xit
End Sub
---------------------------

Some time ago Larry Linton pointed me to
http://www.mvps.org/ccrp/controls/ccrpftv6.htm
which works great.

Only problem is that with my current project there is zero chance of registering an new OCX on a user's machine (corporate security policy).

So I'm back to the plain-vanilla-out-of-the-box control.

Anybody know where to find a decent writeup on the ins and outs of using it.
--
PeteCresswell

[rkc]

"(Pete Cresswell)" <x@y.z> wrote in message
news:j2********************************@4ax.com...

I'm getting nodes into the thing, but when the dust settles, only the root-level nodes are visible.

I know they're there because .Nodes.Count gives the right number.\

But I don't really understand the significance of the Nodes.Add syntax - I'm just slavishly plugging in values.

You appear to be trying to create a parent node and add a child node using
one
statement. It doesn't work that way.

The root node has to be created first using
..Add (, , Key, VisibleText)

Then a child node can be added to it using the root nodes Key value.
..Add(Key, tvwChild, childKey, VisibleText)

If you want to add a child node to the child node you would use the
childKey as the root node Key value.

[(Pete Cresswell)]

RE/

I'm getting nodes into the thing, but when the dust settles, only the root-level
nodes are visible.

I think I've got it doped out.

All available events are not listed in the props dialog - but if you to to a
code window, events like NodeClick are visible.

That, plus discovering that .Item(x) is really a Node....I'm livin' large...
--
PeteCresswell

[(Pete Cresswell)]

RE/

The attached, from the VB help file, may be of use to you:

For sure! Thanks...on my installation of Office 2000 the help files sort of come
and go..and lately they've gone...
--
PeteCresswell