I've had a couple
occasions where deleting the "decodes" files turning out to be the
fix. It would be nice if there was a "reset" choice maybe under
the Decodes Window "view" tab that could delete them without
drilling down thru the localappdata path.
Herb,
Unless your keen to keep the decodes from previous JTAlert
sessions visible, set the Decodes window (via its Settings menu)
to delete all records on startup. Under-the-hood, JTAlert simply
deletes the database file and creates a new file rather than
executing an sql query to delete all records.
If you want the decodes from the last JTAlert session to be
available (so the above is not suitable) and need a quick way to
delete the database when it appears to be malfunctioning, do the
above, restart the Decodes window and then change the startup
option back to your original setting.
