>Hi Dragan,
>
>Count me on your side when it comes to MS behaviour in terms of customer support. But I pay credit when credit is due : win11 is a pleasant for good ol' VFP9 apps. I'd be unfair to say the opposite! But sure I try hard to replace MS stuff like quite a few here on the UT.
>
>I am on my way onto a python+QT platform. But that's a "long and winding road" since I am not certainly looking to replace VFP but to bring to life applications you just could not consider in the VFP+Win-whatever-the-version world.
>
>I am currently thrilled by the recent duckdb+pyarrow combination as a replacement for rushmore when it comes to handling r-e-a-l-l-y large sets of data. A replacement? Well much more than that: duckdb can deliver incredible levels of sql-based data mangling performances on a single machine :-)
>
>Loading millions of records into an in-memory sql workhorse you can build from scratch within a bunch of seconds at most. I can do things I could never imagine doing a fox guy. There are still a few things that rushmore does better than duckdb. But, man, handling literally millions of data (and more should you need of course) within a calculation workhorse on some standard workstation app, in a snap, what a thrill.
>
>I expect to be able to run my PC as a full-time toaster in the way some of the games my kids are playing do via multiprocessing (duckdb+ engine) in a way my VFP applications never did!
>
>Daniel

Thank you, Daniel.
My research into duckdb led me to conclude that it was best used for OLAP, rather than OLTP, which all of my apps do.
Do you think that OLTP apps would benefit from using duckdb as compared to SQL Server?