Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Best Practice - Internal Code field for Heirarchial tabl
Message
From
02/09/2004 10:12:50
Cetin Basoz
Engineerica Inc.
Izmir, Turkey
 
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00937935
Message ID:
00938734
Views:
27
>Hi Cetin
>
>I got your sample code working and have been able to study the results. All in all I was able to understand that cCode as far as the data-entry is concerned is not at all required. My TreeView was based on the cCode order which I have switched to iSrNo (equivalant to your Item or OrderIngroup) and there is no change in data-entry look and feel, atleast yet <g>.
>
>Now comes the fields RootID and Level. As far as the data-entry is concerned I don't think that it will be required, because without them and cCode the TreeView still looks as before. These same 2 in your code are generated on the fly, is that what I am to do, ie. generate them on the fly, so that they do not have any management issues?
>
>Please advise and thanks again for sharing your ideas and codes.

Yes, rootID and level are just created on the fly for treeview ordering. It both helps to collect a node and its children directly from that cursor and/or prevent treeview errors like "Item doesn't exist in collection" (a parent node should be added before adding any child node).
Cetin
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform