>If all the talented people who have commented on this topic had decided to cooperate on a project, instead of arguing about an abstraction, and had contributed one line of code to the agreed-upon objective for each line contributed to this argument, we might have had a pretty slick app here.

Weeellll,
I had added a few dodads and ideas to Etecnologica...,

Lianja used the vcx/scx converter I wrote about 2/3 of starting from nonworking idea at least until 2019 - have not checked since then. Was among the most prolific posters and bug finders back then - but backed out when android native DB and SQL engine was stricken from the roadmap. Hank and a few others known from here debug, conceptualize and add to Lianja.

xSharp already has a couple of lines of function implementation from me - but latest turn of events will implement their SQL engine via reuse of Advantage drivers, which currently are x86/Amd64 only, making my reason for interest, a SQL supporting client/local DB layer along the lines of cursoradapter and tableupdate available on Android/ARM/mobile, uncertain or very late.

Since xSharp is OpenSource, instead of now throwing the towel I stay back a bit - still following, not working on singular functions any more - but if they stay otherwise on track I might try to "out-Pareto" a KISS solution tick(l)ing most of my wishes, as in 10% of the code resulting in >50% of functionality wanted by this ape ;-)

Antonio also active over there - giving solid info, hints and code like he does here, but most other effort comes from their earlier Clipper / Vulcan customers.

Nobody stopping the other posters of this thread to add a few lines of code over there ;-))
Including passionate golfers already fluent in Dotnet ;-))