Hello Mitch,

> > > So the problem seems to relate to the context in which it is called.
> > > But if so, what could be causing this error message? Why would the
> > > same update query sometimes work and other times show this parse error
> > > when in both cases the variables seem correctly set and the
> > > procedure's single input parameter is clearly OK?
> >
> > Since Firebird itself doesn't have a debugger, maybe you should tell us
> > which tool you're using to debug.
>
> I am using IBExpert.
> I noticed that the stored procedure in which this query is contained
> was not actually being called. I have now fixed this so it is being
> called and my program now works correctly. However I am still puzzled
> as to why the debugger seems to be behaving strangely in this context.

As Milan says, Firebird does not have an API to debug server side code.

What happens in these tools, is that they try to emulate the server
behaviour,
they do this by parsing the procedure source and trying to execute the
statements from the client side or emulate them otherwise.

This error is coming from IBExpert, not from Firebird.

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com