>Take a look at PRO 6.0 it has a lot more OOP. Before we start - does it have legacy code? You bet! SBT has been around for 14 years and just rewritting very line of the 100,000 lines would be nuts.
>
>But I like PRO 6.0. It has datasessions. No views that I'm aware of - but I haven't seen all of the code yet. Screens are forms but they still use the event model they invented for fox2.6 although they are just stubs. The same is true for the screens - just stubs that call forms. The only thing I really hate is the way they call GL menu's and reports. The whole gl thing is based on data driven tables - with tokens and other uncompleted items.
>
>John

My last position was in a SBT Pro 3 -> 5 house. We has lost of custom code for binding SBT & TIW. Today they call it ERP.

I avoided SBT programming 100%, and wrote a new interface using MereMortals for their ERP system. Data is still entered into SBT the same old way, but tracking an order through the manufacture process is OOP! 100% views using 1 dbc.

I resigned last Dec, so I was privilaged to never see ver 6. I still get an email via the loop. I laughed when some of the big names were asking how to reference a function in OOP. Those would be senior partners in SBT circles.

I've spoken with John Boy at SBT and he was working on SQL-Server data for SBT at the time. That is down the road 2 + versions mind you but they were looking at how to convert to it. You know that it's just a f'n rewrite and they don't want to do that. It would reak havoc on their business plan.

They have dealer base that is kept in the dark with respect to VFP. Maybe 1% of the SBT developers and resellers are aware of the UT, or MSnews. I give them the mushroom award.


As an end user I got the respect from a vendor when dealing with SBT than any other vendor in this industry. They are seriously dead from the neck up and act like the old mainframe shops of 15 years ago.

__Stephen