Treeview & form calling question.

You are on the right track. With the old TreeView control, the Nodes had a Key. I used to always create a CreatKey() function which Built a Unique key that included the Node Type, such as (R) root, (C) client, (A) address, (E) employee, for example, Then whatever Database keys were necessary to find it, all seperated with pipes. We lost the Key property, but you can still use the Tag to do the same thing, like you are doing. I haven't tried it yet, but think you can actually set the Tag to an object rather than just text. If that is true, you could actually create a collection of Appointment objects and set the Tag to reference the entire object. Then you not only have all of the appointment data available, but any methods of the appointment class. Just a thought. Anybody ever do this to confirm it works?

Thanks for the help!! As I found there is a better way of doing it. Assign the clientid+appointmentid to appointmentnode.tag property. The client Id and appt Id are then available at the appointment node.

Unfortunately, the treeview can only handle text. I have not found a way around this either. What you will have to do, is create a function that will return the client id based on the name. When the name is selected, use the funtion to return the client id then pass it to the appointment form with the date. You could also include the clientid in with the name, then parse it out. eg: 1 - Customer Test 2 - Another Customer