26-07-2018, 12:05 AM
[Disclaimer: I am not a power-user of ANSWER-TIMES, and never seen such an issue myself]
It is not clear to me when the problem occurs, when you re-start ANSWER-TIMES. Does it immediately get stuck, even before opening a database? Or does it get stuck only after opening a specific model database? If the latter, try opening some other database after a re-start; does it still get stuck? If not, then the former database is probably somehow corrupted, and you could try using a backup copy (or try a manual repair of the database in Access). Even if you have not deliberately saved backup copies, you might have a *.bak version in the Answer_Databases folder.
If the problem persists for all databases, I suggest contacting Ken Noble, the developer.
It is not clear to me when the problem occurs, when you re-start ANSWER-TIMES. Does it immediately get stuck, even before opening a database? Or does it get stuck only after opening a specific model database? If the latter, try opening some other database after a re-start; does it still get stuck? If not, then the former database is probably somehow corrupted, and you could try using a backup copy (or try a manual repair of the database in Access). Even if you have not deliberately saved backup copies, you might have a *.bak version in the Answer_Databases folder.
If the problem persists for all databases, I suggest contacting Ken Noble, the developer.