George:

I don't have enough history with VFP to comment, but it seems that it took MS until VB 5.0 or 6.0 to get anything near compiled executables. (Delphi was compiled at 1.0 and very fast). Delphi has always used pointers and standard Windows messaging. Borland 7.0 for Windows with OWL even had these features (circa 1992). Delphi also has had built-in bound data-controls using the Borland Database Engine. Many 3rd party developers created bound controls without all of the overhead of the BDE.

The other thing I'd love to see in VFP is a market for components like Delphi has. These are controls that usually come with source code. If something doesn't work and you don't have time for the provider to fix it, you can debug it yourself and see where you went wrong. (This is usually what happened to me. Component was fine, but my code was faulty.

After 7 months, I'm actually getting used to VFP's way of doing things, but it does limit access to standard Windows features. MS is the only company that can establish real "STANDARDS" that everyone should follow, yet MS has 2 very successful products, VB & VFP (well at least 1) that seem to not follow the MS standards. I find it refreshing that MS seems to give the VFP team the flexibility to try to develop a great product in the best way they know how. I would never call into question a development teams dedication and interest in providing quality products. HOWEVER, I do question whether the developers have enough freedom without Management interference. Why doesn't VB allow OOP features like inheritance? Can't be done? VFP did it. I can only assume there is some other reason. Like product definition that is done by management.

Let's see what's in 7.0.

Mike