Just ignore it - I've seen this happen before even on perfectly valid SQL
statements pointed to 4D's own engine.
Sometimes you can tweak a line or two in the statement and the error triangle
icon will go away.
--
Jeffrey Kain
jeffrey.k...@gmail.com
> On May 3, 2018, at 7:52 AM, Uist Macdonald via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> I am developing a V16.6 app which uses MSSQL as the backend database.
> I have a slight problem in that I am storing Unicode in NVARCHAR fields which
> 4D indicates is a syntax error next to the line, although it actually works
> fine in practice.
> The app compiles OK.
**
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
**
