All I remeber are the build #s seems to keep track with the # of days the program was out, or a new build a day! {early Pro series}

I don't remember them starting with dB4, I thought that it was FP2.5. At that time FP was the chose compiler for the vision point? Your end user run time was always FP 2 or 2.5.

I do know that wroking with their code is a nightmare, and that it has always gone against the FP industry standard. Then never wanted to compile an exe, dbc's were not used, and the marco substitution from HELL.

I remember helping an individual in the developer school provide a simple enhancement. End user could not distinguish the company # she was in. We went to the SBTBAR and modified the disply of the desktop graphic to become a pool ball that showed the # of the ball, as well as a color. After the fact the instructor was impressed that we could change that by company #.

Bringing home the point that the thing is too complicated in rhetoric and back-ass-ward compatibilty. A re-write is about all that they can do, and this time keep the same design team on all the modules instead of teh PR team, GL and all the other crap team. Very evedent in looking at the code, table design, and normality. The "other crap team" never understood normaility, redundant data and wasting tons of storage space.

>Will SBT proc go away completely -- MAYBE but I believe the current thinking is that it is faster to use small little programs in some cases than classes.

I think that SBT has to come to grip with classes, they are for more than containers! Creating a bizobject that can dictate data sessions as well as hold key processing is only better to the nighmare of all the ?_ procedures that recursivly call one another!

By making them a SObizClass where this class is droped on all SO Forms they would achieve the same results. this could also end the bastardazation of the form designer that was implemented in ver 5.

I don't sell SBT anymore and glad not to. It's got to be one of the best ways to handicap a good developer. Take away all the good tools, lock yourself in a dark closet and hope that the "LOOP" an help you out.

__Stephen Russell
SBT USER and ABUSER


>If you recall the history of the PRO series then the changes are not so far fetched.
>
>1. They started with dBaseIV (remember Ashton-Tate). SBT decided that the platform was not selling or to buggy - and tossed it out the door. (lost lots of money)
>
>2. Used Fox 2.5/2.6 to create PRO 2.5 with a complete event handler and many other interesting features. Nuts to work with.
>
>3. Started devel with VFP 3.0 for PRO 3.0 the changed to VFP 5.0 to complete. Made so many changes that all the old PRO 2.5 code mods had to thrown away.
>
>4. And now we have VFP 6.0 and the bases classes are so different that it is crazy to continue with the old PRO 5.0i model. And again we will throw out the old mods.
>
>The only thing that has stayed around has been the tables.
>
>Will 6.0 have more OOP --- YES
>
>Will SBT proc go away completely -- MAYBE but I believe the current thinking is that it is faster to use small little programs in some cases than classes.
>
>Will the accounting module structure stay -- I think so because of the way they sell them. You know buy one module or all.
>
>Will they add more tools to integrate. You bet.
>
>John