>advances since their major upgrade 3 yeares ago (PB 6?). Another place where VFP beats them is support for both remote data and local tables and views with the ability to transparently [to the user] switch between the types.
>>
>
>Actually, in my opinion, the PB DataWindow is as powerful, if not more so than the VFP views... DataWindows go further by defining, not just the SQL but also the Visual aspects of the data retrieved.
>

I do not understand what you mean by the Visual aspects of the data retrieved.

>In addition to the DataWindows... another very powerfull feature of PB is the meta data that PB adds to every database when you access that data with PB.

I use SDT, so I have meta data on local tables and views as well as remote views and all the documentation features. What about OOP and inheritance? Still looks like the same PB as 3 years ago except for meta data which SDT has been doing for years at a more affordable cost including the cost of VFP.

My biggest gripe is with the VFP View designer. :)

I do know PB is definitely a solid product, but what it all comes down to, ultimately, is what we know and what we have become comfortable with using.