I don’t think reloading a database from Use SQLite functions, as intended. I’m not sure how it can, and maybe it should just go away. (This likely applies to Use SQL Server, too.)
Use SQLite is a synchronized copy of what is in the .gsjdb file. It’s a real time backup. (A really cool backup, at that.) If you are connected to it, all is grand. Connecting to a database after it has been disconnected asks you for a new file. You have the option to replace the existing one, which will result in it being reinitialized. All is lost.
I attempted to outsmart Grindstone and failed. (Good job?) Anywho, after breaking my .gsjdb file, I attempted to recover the data from the sqlite file. I renamed the existing sqlite file, started up Grindstone…creating a new file with the old name and then connecting to it. (Connecting initializes the db, hence, rename and save it.)
I then exited out of Grindstone and renamed the sqlite files, returning the old one to the original name. My intent was to restart Grindstone and it would reconnect to the sqlite file without reinitializing it. I would then reload my data from the sqlite file. Unfortunately, this resulted in errors that I was unable to get around. (Sorry, I don’t have the errors any longer.)
Have a good one. (Keep working on 5.0, but this might be something to consider in that effort.)