Greetings @woz_s - looking back through the history of this issue, i see a couple of things to share:
- the Filemaker Pro scenario mentioned in the original post was specially handled. The semicolon is not actually removed from the generated SQL, but the semicolon is stripped "under the covers" before submission to a Filemaker Pro database.
- i see an existing request for the preference/checkbox mentioned here, but it has not been implemented yet. I bumped it up and mentioned Presto as another database that isn't working with the current implementation. I hope it can be handled in a future release.
For now, the workaround you have found to remove the semicolon is the best solution i can offer.