Tim Aside from the missing colon - which had been corrected - I also believe the statement is valid, since it's working in another method in the DB. To eliminate copy and past errors, I retyped the SQL block, but still got the error.
What I didn't do is quit and restart 4D - after that the code ran as expected. Go figure. On Wed, Nov 1, 2017 at 12:02 PM, Timothy Penner via 4D_Tech < [email protected]> wrote: > > I think you have multiple issues with this SQL Statement. > > I was wrong. I didn’t fully understand the SQL statement at the time of my > last reply, upon further inspection it seems the SQL is valid (apart from > the missing : in the variable reference). > > There must be something else wrong, like using this statement inside of a > SQL function {fn} call for example. I think we are missing some context > about how you are using this method, because executing this code in a > method by itself is working in a sample database here. > > -Tim > > > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: http://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** > -- David Witton ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
