Such a message after running Settings.

Do I need to create a MySQL database?
Hello W7DRMW7DRM wrote: 23 Jan 2020, 20:49 No, you don't have to be using a MySQL database to use the JTAlert Beta 0006 integration with V2. But it looks like you may have selected MySQL in the JTAlert Logging, Log4OM V2 settings? Check that first.
Doug - W7DRM
I had same issue with an early version of JTalert and told Laurie about it, try the latest updatesq9jxb wrote: 24 Jan 2020, 05:56Hello W7DRMW7DRM wrote: 23 Jan 2020, 20:49 No, you don't have to be using a MySQL database to use the JTAlert Beta 0006 integration with V2. But it looks like you may have selected MySQL in the JTAlert Logging, Log4OM V2 settings? Check that first.
Doug - W7DRM
I'm using SQLite instead of MySQL, and Settings in JT Alert does not open.
I stayed with JT-Alert - 0001 Beta
Regards
Hellova3vf wrote: 24 Jan 2020, 14:23 If JTAlert is not opening, download beta 6 again.
Make sure to use the Log4OM v2 tab in JTAlert, and point it to the SQLLite or MySQL file you are currently using in Log4OM.
73 de Vince
Hello DanielleIW3HMH wrote: 24 Jan 2020, 15:44 Log4OM current connection is reported in the l4ong.status file in the settings folder (HELP -> OPEN CONFIGURATION FOLDER)
this should reflect current configuration settings.
Please check if that file is correctly pointing to your actual database archive.
In case of errors please let me know, you can safely delete it, Log4Om will regenerate on next start