>I don't believe it should take M$ that much effort to do for VFP what they have already done for Access97. VFP reports are an embarrassment, for that reason alone. Here we are always saying that VFP is the real OOP environment, but it has this gaping hole in its object model. I don't really know if this issue is the most important one in VFP, but M$ should address it because what we have now is just the wrong way to do things.
>
I think I would have to agree with you here. Non-OO reports and menus break the model, and decrease VFP's functionality by that much. Is it critical that they be made object-oriented? Probably not - we've all had to learn to use them the way they are, or adopt some other tool to do the job required. But where would be we if the reports and menus HAD been OO'ed from the start?
If it can be done without taking away from Really Important Stuff, the VFP team should do it. That's my vote.
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.
