>Are you implying you know exactly why those features were added or exposed?

I know exactly why they were added; because the first implimentation was incomplete. This is with respect to the MT-DLL. That was both a new feature and a bug fix.

The session class was added at the urging of development community. That was squarely a new feature.

>
So are features like Grid Highlighting and Auto incremementing fields. Can your users tell if primary keys are being generated automatically by VFP or by the Default Value of the field? My users don't even know there is a primary key there! Same thing goes with the grid lines. While the features do round out the product, make it simpler to learn and easier to user, they add value for teh developer. Just like Intellisense.
<

It is clear you are taking bug sips of MS Kool-Aid now.... < bg >....

My comments were directed at the statement that SP's are ONLY for bug fixes. History would indicate otherwise. dBase had auto-incrementing PK's 4 years ago. The way Grid highlights work - or don't work as the case - are illustrative of the little BS things that have not worked correctly for 5 years. Given the choice between DB-events and a properly working grid, I will take the latter.

The bottom line, these features should have been in the product a long time ago. As for how intellisense is implemented, it still does not work as well as VB's. Sure, you can go deeper in a hierarchy, but there are too many oddities in the VFP intellisense.