Log4OM

Jim,
We are still waiting for your support request and the information therein.

If you have already resolved the problem please let us know what the cause and what the remedy was.

For the information of all users!

The support request for this issue was received on Saturday at 15.36 and responded to as below at 08.21 today Sunday

"Hi,
it seems there is a MySQL parameter working in strict mode, and this is not fully compliant with the query created by Log4OM.
I will fix the query on the next release, to avoid this case. You can try fixing the issue by changing a mysql parameter, as described here

http://stackoverflow.com/questions/3411 ... y-in-mysql

73
Daniele"

This appears to manifest itself only when running Log4OM in a virtual Windows environment on a Mac computer

And Daniele figured it out. It's a problem with MySQL. There are 2 lines that needed to be run and now it works as expected.

http://stackoverflow.com/questions/3411 ... y-in-mysql

This is the reference he sent in case it might help anyone else that has this issue. He did say that he will fix the query in the next release.

73,
Jim, WD9HBC