Hi John,

>If I'm reading this correctly - you used an old machine to run fox and a new machine to run duckdb??? Even if >the data used on the new machine was larger I would expect the performance difference between the >machines might be a such major difference as to not be meaningful. Duckdb as an in memory replacement >for SQLite sounds interesting - but you have to recall that SQLite also has code to support multi-user and
>persistent files. So I wonder if DuckDB will stand up to the same demands.

You are not reading correctly, more to the point, I did express myself correctly. I'm 100% gallic and my English is certainly convoluted or worse at times:-)

Sorry, I read your earlier statement incorrectly. That said, I use SQLite ::memory as a replacement cursor (as in Fox). Normally the data size is a single record or small enough not to be considered an issue with respect to Ram. So I would be interested in how long it takes to create the DB in memory. Normally I have to create the model in advance and then populate.
Johnf