Bingo!
I erased the SQL command and typed it on one line. Works find. Broke
it up again with linefeeds. STILL WORKS!
Now I wish I had commented-out the original command rather than
replacing it, as now I don't know what the rogue character was!
Grrrrrr! (I need more sleep!)
Thanks for your help. And thanks to Axel too, who e-mailed me directly
suggesting the same thing.
Cheers,
Richard
"Ross J. Reedstrom" wrote:
>
> Richard -
> I recently tripped over some whitespace sensitivity (that shouldn't be
> there!) involving line-endings in queries. Could you try your UPDATE all
> on one line, and see if that solves it? I haven't been able to replicate
> my problem with my current set up (in order to file a bug report). It
> originally happened with a demo system we had set up at a meeting. Once
> we got back to the office, everything worked fine, of course!
>
> We got the same sort of 'paser error at or near ""' line in the log,
> but when I looked with the right editor, I say that there was a control
> character (either ^M or ^R, can't remember which) between the quotes.
>
> Ross
