Subject | Re: [firebird-support] Unexpected End of Command |
---|---|
Author | Mark Rotteveel |
Post date | 2013-11-03T09:31:39Z |
On 2-11-2013 20:01, Andrew Gable wrote:
queries? That saves a lot of hassle like escaping and keeps things more
readable.
...
complete parse, eg missing a quote or closing parenthesis does this.
At first glance there doesn't seem to be anything wrong with this.
Mark
--
Mark Rotteveel
> I have a problem that has ONLY just started to happenThe first thing that I wonder is: why aren't you using parametrized
>
> When ever I run the following SQL command from within my software
>
> THIS has been working for the last 3yrs ever since I moved over to
> Firebird (I have software running the same command
> and they are working fine)
queries? That saves a lot of hassle like escaping and keeps things more
readable.
...
> I get the following error messageIn general it means that the parser ran out of input before it had a
>
> Run-time error ‘-2147467259 (80004005)’;
>
> [ODBC firebird Driver][Firebird]Dynamic SQL Error
> SQL error code =-104
>
> Unexpected end of command –line ##, column ***
>
> ## and *** always change no matter what information I send.
complete parse, eg missing a quote or closing parenthesis does this.
> This is an example of what I am trying to store into the database (Debug...
> print out of what i am sending)
At first glance there doesn't seem to be anything wrong with this.
Mark
--
Mark Rotteveel