URGENT!! Anyone aware of limitations with the Treeview ActiveX control??

[NickP]

Anyone aware of limitations with the Treeview ActiveX control??


I am having issues when using 2 of them on an Access 2000 form. One on one tab and the other on a seperate tab. When I click to go between tabs I get a messed up treeview control that is listing my nodes wrong. Then I get a Doctor Watson error. There is about 40 items listed in one and about 100 items listed in the other.

Has anyone seen similar problems and have an idea of what I could do to solve this issue??

Is there a better control out for that??

Is there an updated MSComctl.ocx out there?? If so, where could I find it??

???

[vbmom]

I use Infragistics' (used to be ProtoView) DataExplorer which is an ActiveX control similar to the MS TreeView control. I have seen Dr. Watson only when I've programmed very badly. Things like pointing to nodes that don't exist, or referencing some property that has not yet been initialized.

I suggest stepping through your code and trying to pinpoint where it's happening.

Perhaps you can insert the treeview-loading code into a regular form and see if that changes things or helps you debug.

[NickP]

My code is fine. I know this because when the form loads the treeview data is fine. However when I click on another tab then come back the treeview data is no longer correct. No code of mine is ran when I click one tab and then click back on the first tab.

I have also found that some computers get the doctor watson errors and some do not. So now I am totaly not sure what the cause of the problem is.

[vbmom]

Ok, I'll admit I know nothing about programming in Access, however, I argue that perhaps some kind of code is being run when you 'click back' to the first tab. Is there some kind of Activate or GotFocus event that the tab control (or whatever it is the treeview lives in) has? Again, I ask, have you stepped through the code (can you with what you're doing)? If it's happening on some computers and not others...I would suspect a memory problem and indeed some kind of wacky call to treeview control to do something it can't handle.

(I have seen some computers express Dr. Watson and some express one of those message boxes saying "the memory at location hex_num cannot be read" for the same problem. I think that depends on computer resources.)

I'm sorry, I'm really no help, but I thought I would just reply and express my condolences. I gotta finish cleaning the bathroom now.