lbross
commented
2 months ago I am unable to recreate this issue. Cat is correct in her assessment of the problem in that the error means that BioSum couldn't find the temp database in her AppData directory. It is not unexpected that there were many other temp databases in that directory as that is how BioSum does most of its processing. When BioSum is closed out, it deletes these temp databases so Cat was wise to check for the database before closing the application. I don't know why the database was missing and have not heard any other reports of this issue. I will leave this issue open in case the problem recurs. I don't want to spend too much time digging into this as these tables are in the fvs_master.mdb and this database is included in the next round of conversions to SQLite. My advice with BioSum is to save often so that you can never lose too much work if it glitches.
I was trying to add and save prescriptions to a project given to me by Jeremy (CWI). I added the 12 prescriptions to the list and when I went to save, an error message came up indicating that BioSum was looking for a temp database that did not exist; thus, the list would not save. When I looked into my temp folder on the C drive, BioSum had been creating a ton of temp databases throughout the afternoon, none of which were the file BioSum was looking for. I have attached a picture of the error message.
I exited out (lost the list sadly) and saved the project, closed out, and got back into BioSum. After doing this, I was able to save prescriptions.