Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Problems With TREEVIEW OCX
Message
From
16/06/1998 11:01:56
Bob Lucas
The WordWare Agency
Alberta, Canada
 
 
To
16/06/1998 03:41:55
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00108539
Message ID:
00108673
Views:
51
>We have a serious problem with the Treeview OCX :
>
>1. In the debugger, any attempt to enter the "node" object crashes Visual Foxpro (illegal operation...)
>2. When repeating the following process several times, something wrong appears :
>
> A. All the treeview branches have been expanded (with the mouse)
> B. The whole structure is cleared with "ole_TreeView.Nodes.Clear"
> C. We try to rebuild the structure, with our procedure.
> The fist line is always OK .
>
>The bug : Sometimes, when trying to open he first branch, at the first node.add, the message appears:
> "member nodes does not evaluate to an object" ???
>
>On my machine, this happens after several attempts (4 to 20).
>When the structure is not expanded, it never happens.
>When I collapse the tree with the mouse before clearing, the bug still appears !
>On some other machines, with the same application and the same OCX, it does not seem to happen !
>
>We currently use COMCTL32.OCX 591 kb 19/07/97 17:00
>Registering it again with regsvr32 does not help !
>Fox.reg does not help either !
>
>Could anybody help me ?
>
>Thank You !


There is a bug with the treeview control within Visual Foxpro. It is with all versions of VFP including 5.0a and all service packs. I went through Microsoft Tech Support and provided a very small project file and forms that identified the sequence. My situation had multiple tree view controls on multiple pages of a pageframe. Clearing the current data, reloading new data and displaying it caused no problems until a MODAL form was displayed and closed. After displaying the modal form the node.add method of the second treeview control that was being refreshed caused a GPF. Modal forms seem to cause some problem interaction with ActiveX components.

This has apparently been fixed in VFP 6.0 (I haven't tested it yet.)
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform