Hi Daniel,
Sorry if I am a bit slow on responding, taking some time to go through every fox forum (that I am aware of) and respond in a meaningful manner.

> After so many years in the VFP world and still, losely, sticking to it, I resort to SQL engine power for anything resource-consuming. No C-level code, no external library.
> This may at time be un-usual un-academic use of SQL.
We still have many VO developers using X# as a front-end to DBF. I however have moved on to SQL and PostgreSQL as my preferred Db. There are in the Pearls forum on X# examples of using SqlLite with X#, both with Ado.NET and Entrity Framework.

> As Hank and Fay have mentioned, I am not alone at this workstation-side level level of VFP.

I am also actually quite fond of DBF for desktop applications. Unfortunately it is not that easy when doing work for big corporations that has no-go policies for anything done locally.

> The perspective of a powerful 64bits local in-memory engine with top-notch performance at hand would definitely make the Xsharp attractive. Sort of the the same
> very same way sqlite is attractive in python. The sqlite integration in python is really impressive(*).

I think we just need to be patient, these features will be included, but the basics first need to be in place, which X# is getting close to from a VFP perspective. The beauty is that yes on the one side we want to protect our legacy code, but X# also provides at the same time the functionality of "new" features that we can use during enhancements/new projects.

> (*) Within python, sqlite can be used as a local engine (in memory), a way to run code in a smart way (extending the sqlite engine with C or python
> udf-s) and a persistent file-format for backup.

There are also some X# guys that uses Sqlite in the same manner.

Johan