>I agree wholeheartedly with your opinion.
>
>The main differences between Visual FoxPro (and VB, PowerBuilder, etc) and C++ is that if there is a bug in the VFP environment it is the toolbuilders responsibility to fix that bug and the process may take a year (or more) and sometimes the bug never disappears.
>
>With C++ you often have the option for the full source for the tool library so if a bug is uncovered a) you can determine the exact nature of the bug and b) you can fix the library bug and recompile. While both of these C++ options are not for the novice, I find security in knowing that if there is a bug I at least have the potential to fix that bug in my app.
>
>Another reason I prefer C++ over VFP (VB, PB) is that it is more democratic. If I have a problem with the C++ compiler vender (ie Microsoft) I can relatively easily port my app to something like Borland C++, Symantec, etc. You do not have this capability with FoxPro and the like.
>
>The final reason is that C++ is a general purpose powerhouse and VFP is not. My current project is a record keeping product and I have been continuously frustrated with VFP. My normal programming cycle is to dream up some concept (within reason) and then implement that concept. In VFP I tried to display parent/child relational hierarchy using the supplied active-x treeview. After investing roughly 10K, I ended up trashing the effort due to deadline constraints, numerous bugs in VFP (and a control that had bugs and was designed for VB and without VFP in mind) and a lack of knowledge on my part as to how VFP works internally (which of course is not documented).
>
>So, my future strategy is to finish this product ASAP and then port it to C++.


Do I understand correctly?
You spent $10,000 trying to make a tree view work?

Chris