My last comment on this - honestly. Yes, you do not understand ODBC. Common misunderstanding. ODBC is not restricted to just SQL databases; you can use CSV, text files, etc. Info here: https://en.wikipedia.org/wiki/Open_Database_Connectivity
Back in the day I worked with Borland, MicroRim, etc. on all of this stuff and even with proprietary databases, you could usually have an API to access the data directly. Proprietary compressed databases are nothing but a headache. I still have some clients who use them now and what they gain in speed (like you really need that for Davis weather data??) they lose in interoperability. BTW when I used WLK I had all sorts of neat routines to regular extract until J Ruys came up with the SQL interface. Sadly, that was an unsupported, one-off. Nice work though.
Like I said - I'm done. WLK files are archaic, as is the software. IMHO of course.
Sorry, I can't resist answering your "you do not understand" comment.....
I understand ODBC. I never said SQL. I did say "database management system
S"
And, an ODBC driver could easily be written to access any .WLK
file (singular). Any single .WLK file can be viewed as a database management system.
I do quite agree with your comment about proprietary systems. And that .wlk is archaic. And yes, hanging onto them for too long is a big headache. [But I never said that compressed files like .WLK were needed for
speed in a weather system]
Footnote: not that it matters, but I have an MS in Computer Science, hold a CCP in Systems Programming, and spent most of my career in IT management and QA. So, like you, I have "been there and done that".
Enough of this nit-picky off-topic stuff. Alternatives are available for the choosing.