Hello Roy.

Sorry for my unprecise comment.

1)
The error is the same as in "An error was found in the statement at line xx and column yy (Expected FROM but instead found  )".

2)
The server character set is Unicode.

3)
In short:

In the meantime I created completely new folders for my database and created completely new SQL statements and jobs for testing where I entered the commands manually (not pasting in).
Result: everything is working!!!!!

I switched back to my original session / database and created completely new SQL statements and jobs for file deleting where I entered the commands manually (not pasting in).
Result: everything is working!!!!! I played around with different Store names and file names and everything is running.

Your idea with manually entering the commands and not copy and paste was the right way! I don't understand why. I even had edited and modified the commands manually a thousand times.

Anyway - a million thanks for sharing your brains and time!!

Joe

Joe


One of my guesses at the start was <<You may be introducing some banned characters which cause the SQL parser to have a hissy fit.>> so it looks as though that was right. You get a non printing character in there and some are very difficult to spot and difficult to get rid of because you can't see them.

I'm pleased its working for you now.

Roy Lambert

Joe,

<< Result on execution:
ElevateDB Error #700 An error was found in the statement at line 4 and column 19 (Expected FROM but instead found  ) >>

Any time that you see an error like this, it's almost always due to a weird control character, most notably #0, getting embedded in the SQL somewhere.  That's why you see the "blank" in the error message where there should a keywork or token.

Were you pasting this SQL code in from somewhere else, or writing it directly in the EDB Manager ?

Tim Young
Elevate Software
www.elevatesoft.com