Rick,

What makes a FP cursor special is its automatic memory/disk spanning. Whether people like it or not,

use mylookup order myorder

offers a smorgasbord of options for very little risk or cost. It isn't the VFP syntax that delivers the benefit but the automatic memory/disk spanning. For a start, it allows efficient 500,000 row static lookups at app end or middle tier with no network cycles or SQL load. While this is well understood in VFP, I agree there are legions of developers out there for whom such local data stores would be seen as unpredictable local memory hogs, best avoided in favor of Server-side processing. Well, in VFP you can go either way. I don't want to lose that.

i see that some of the Python-spawned languages are starting to offer memory/disk spanning. That's smart. Hopefully that is what MSFT means by a "local data engine" as well.

To be clear: this isn't about "VFP is best". It is about improvements to MSFT's designated successor language- improvements that may well be enjoyed by other developers who may have seen a role for a local repository but decided it must be bad design. To me it feels a bit like the belief that diesel engines are noisy, smelly things for trucks, not luxury passenger vehicles. It doesn't have to be that way.

Regards

j.R