Please note:
This page requires I.E. 4.0 or later. You also need Microsoft Treeview
version 6.0 (MSCOMCTL.OCX)control registered on your machine. If you
have Visual Studio or Office 2000 Developer, it should already be
installed.
This example uses a selection of data from a Bill of Materials database
Click on the applications to view further details
The treeview has been loaded using the table below to produce a
heirarchical structure.
ID
Parent
Application Name
5
10009
KS2100 Core
6
10009
CPS (pre-ADAS)
7
10013
OCS Basic
8
10009
Engineers Workstation
9
10009
System Manager
10
10009
Printers
12
10009
Consumables & Test Eqmt.
18
10009
Data Logging System
20
10016
Roll Load Regulator (177)
21
10018
HGC - Position Txrs - Sony (177)
25
10015
Gauge Error Feed-Back (GEFB)
27
10016
AGC - Basic (177)
31
10015
Speed/Tension Interface
40
10011
AFC Basic (177)
41
10031
WRB Regulator
46
10025
ISV Sprays
50
10026
Vidimon up to 29 rotors
60
10030
KM Standard Set-Up/Logging Link
101
10014
OCS - Mill Mounted
1009
10020
Eberline 210/215 Gauge Link
10009
-
Basic Platform
10010
-
AGC
10011
-
AFC
10012
-
LEVEL 2 & Links
10013
10009
OCS
10014
10013
OCS Location Specific
10015
10010
AGC Outer Loops
10016
10010
HGC
10018
10016
HGC - Position Transducers
10019
10010
Thickness Gauge
10020
10019
Setup Link
10021
10015
Production Optimisation
10024
10011
Shape Measurement
10025
10011
Sprays Control
10026
10024
Vidimon
10030
10012
Setup & Logging Links
10031
10011
Work Roll Bending
10032
10011
Steer Control
20115
10019
Thickness Gauge - Installation Coordination
20124
10019
Thickness Gauge System
How it works
The table is opened as an ADO recordset and all the
applications without a parent are added to the root project
node of the tree. After each of the root applications are
added, a recursive procedure is used to search for descendants.
The client VBScript (use View Source to inspect) is created line by
line by the server side VBScript.
