Just check ones with baseclass label then. For the 65000 thing, if you think it'd hit array limit then I suggest not to try with a treeview at all (unless your users like to take coffee breaks during form load - or alternatively you could utilize 'populate on demand approach', check UT magazine June 2001 issue).
Cetin

>Ok Cetin,
>
>Here is what thought.
>Tables are eaiser to populate with treeview So i put a cursor.(Fear incase exceeds 65,000)...:)
>
>If i put a property say show_in_treeview when .t. i could simply scan for the show_in_treeview and put the required ones into the treeview. There are so many labels just as markers or just to clearfy where the users are. I dont wish to include all those in to the treeview which would make it unnecessary
>e.g.
>The page caption is Drugs
>and a container and in it
>and one Textbox has a associated label marked drugs
>and second Textbox has a associated label marked Intake.
>
>Now the treeview would have two entries Drugs.
>
>I want one with the label drugs and label intake so the I could shift the focus on the associated textbox with the page in question being activated.
>
>So I think a property would be much eaiser.
>Too bad i did not create all of them through classes.
>Now only way might be to hack the scx change the baseclass to a custom baseclass with the property added.
>I could add a array and then would again have to maintain it as and when i delete/add the controls. but this way I need not worry about maintaining any thing.
>
>Any more ideas are welcome.