>> There is no documentation on applying Parent-child relationships in the 3.01 docs. Period, end of discussion. If you are using a later version be happy that they updated this part.
>
>I have an old copy of the 3.00a developer's guide, on page 42 there is a section on defining parent-child business objects. So there is some documentation, but I guess it is not complete enough for you. You should also look at the samle application, I believe there are some examples in there.
>
>As for using a later version, I can understand you explanation (although I don't agree) regarding not going to VFP 6 and MM 4.0, but why are you stuck on 3.01? 3.02 was a minor upgrade but may have solved some of your problems. I don't think you should be comlaining too loudly when developers are enhancing their products and you choose to stay with the older versions.
>
>Kind Regards,
>
>Mat
One reason I am pissed off is that we paid for a year of upgrades when the company bought the developers license. Kevin Changed HIS end of the deal several months ago, no longer updating for free. As far as I know 4.0 only works with Visual 6.0.

My company will not buy any more upgrades of M$ products. I can not (nor do I want) to change thier minds. These upgrades are getting very costly as they add stuff I don't need and move things I need to "Enterprise" editions.

BTW, I am not overly upset at MM I am upset at the lack of backward capabiltiy in 4.0. It would have been much better to flag the non-compatible code or some other thing than force companies to buy a (to me) marginal upgrade in functionality from M$. Many companys still use VFP 5.0, In fact I really don't know anyone who's company has ported all thier apps to 6.0.

Thanks for the advice and after 2 hours of tearing apart the example, which BTW does have a major bug ( look at PostInitHook and the VPARM_NAME and EXPR which will run-time error on you, hard code that to 1 and 2 and it works), I got the Parent-child working.

No hard feelings, but I do buy frameworks to make my life easier.