I think I found a workaround for me, but it is quite AWKWARD!
First, I tried using ArcGIS Pro to create an SQLite geodatabase. Not sure if I did something wrong, but I ended up with a folder with a .gdb extension full of files. There was no single file database that I could make an ODBC connection with.
My next attempt was to create an SQLite database directly in SQLite and gave it the .SQLite extension. ArcGIS pro recognized it. I was able to connect to it with Catalog as well as to my SQL Express database. I did a cut and paste of feature set table to put a copy in the SQLite database. Unlike my SQL Express database where I could not edit the layer, I was able to add the same layer from the SQLite database and edit it just fine.
My next step, like you was to download a free SQLite ODBC driver. I was able to create a DSN just fine, but when I tried in MS Access to link the table, I got an error that started out "_SQLSpecial....". I tried with several tables including those without geometry and got the same error. The ODBC driver I downloaded was from GM Software. I looked at the one from the .de site, but because it was http, not https, I was a bit spooked and looked for malware reports. I'm not sure if they are legit, but I found some that indicated SilverFox, so I did not download that one. I considered trying the Devart one, but decided not to because I did not want to pay that much for it.
My workaround is this: In the old days, things were straight forward. I used an MS Access personal gdb with ArcMap. My forms, queries, and reports were in Access and I used ArcMap for the geo tasks and maps.
I had previously converted my MS Access database to SQL Express. I had to deal with some differences in time and date storage, but it as pretty straight forward. MS Access became the front end with the queries, forms, and reports to linked tables that were stored in SQL Express. My plan was to use ArcGIS Pro for the geo tasks, but found I could not edit using it.
(To be fair, perhaps there is a way to create the SQL Express database in a way it can be edited and I did something wrong creating it, but I can not find a clear way to do that with only a personal use license (I have one for both ArcMap an ArcGIS Pro).
My workaround is to keep two databases. My working database will continue to be the one in SQL Express. In addition to the MS Access front end for it, it also supports an web site where non-geo data is published from it. My second database will be in the single file SQLite database or perhaps the .gdb folder database. Either way, I can connect to all of them in ArcGIS Pro and edit either of these. When map edits are needed I will do it with ArcGIS Pro in one of these two SQLite databases. I will then use Catalog to copy the updated table to the SQL Express database. I will need to do this each time I make mapping edits. I will also need to uses the apply symbology tool in the Geotools to get my symbology back from the original. I can then delete it.
As I said, this is an awkward workaround but it is the best I have unless and until I can find a way to edit an SQL Express database in ArcGIS Pro with only a personal use license.
