This is a strange error which I have had Epicare look into and they have pushed it back to be probably caused by my BAQ - even though it is happening on a few I have created.
In BAQ Designer (Cloud version), if I join two tables which do not have an index or automatic entry for Matching rows in Table Relations, I add them manually, starting with Company then find a common field such as JobNum etc which shows as an “And”.
Then I add fields into my query to get a set of results.
The issue is, when I come back to my BAQ to look at again, I hit the Test button and I get the error “Severity Error, Text:Bad SQL statement” which has been caused by the 2 fields swapping places causing the “And” to jump to the top and spoiling the logic. I reverse it to fix and can then run my Test.
But it is happening often and on a few BAQ’s which is irritating to say the least.
Has anyone seen this before? I was of the opinion it only started happening since 2025.1.11 but I may be incorrect.