Gary,

Actually, both VB .NET and C# have leap-frogged VFP's OOP capabilities. Here are some of the OOP features found in both languages that I wish were in VFP:

* The ability to raise custom events
* Subject / Observer event handling model
* Defining and implementing interfaces (you can only work with COM interfaces in VFP which is a serious limitation)
* Static class members (they belong to the class rather than the instance)
* Overloaded methods (allows you to gracefully handle optional parameters)
* Abstract classes and methods (you can fake these in VFP, but it's not elegant)
* Structures (lightweight "classes" that are value types rather than reference types)
* Indexers (the ability to treat a class like an array)
* Operator overloading (the ability to redefine the meaning of operators for your custom types - C# only)
* Strong typing - This is a big deal...although VFP 7 introduced strong typing to VFP, it's not true strong typing enforced by the compiler...it's only for IntelliSense and COM Type Libraries). Strong typing allows the compiler to catch a good number of programming errors (as opposed to finding them at run time).

Although .NET has many OOP advantages over VFP, VFP is still does data better! However, now that Alan Griver (YAG) is on the .NET data team I'm interested to see how this improves ADO.NET.

Regards,