>Among the list of new 'features' in Visual Basic.NET:
>
>- Default properties are no longer supported
>
>- Tests using AND and OR can now be short-circuited
> (only the first condition will be tested if that's all that's necessary)
>
>- Functions use the RETURN clause instead of the function name
>
>- The Set keyword is no longer necessary for object assignments:
>Set o = CREATEOBJECT("Whatever.Whatever")
>is now
>o = CREATEOBJECT("Whatever.Whatever")
>
>- Inheritance
>
>- Variables are passed ByVal by default
>
>
>Anyone else see the pattern?

And BV is going to have an equivalent to our command window...

Access2000 can access SQL Server natively and the look and feel is a lot like our browse window...

And ADO+ now references fields as Table.Field ...

And lets don't forget that Rushmore was added to Jet (and SQL Server too?) long ago...

So, I expect that soon ADO+ will have seek, scan for, calculate for, locate for and so on...

Now, being the ADO recorset based in the VFP cursor technology, why we can not use it directly as a cursor? If so, that will give us a lot of [more] power...

What about a select ... to [XLMRAW] [XMLDTD] [XMLSCHEMA] , same thing to copy to and append from...

And a select ... to [varname] will be a killer giving the functionality of EncodeDBF in one command.

What do you guys think?