Hello Helen, Nick,

> > > Is this the same problem Martijn posted or are you hijacking his

thread

> > > with a different problem of your own?
> >
> >It's the same problem, It only occurs using his database management tool
> >and we didn't know what the error message meant
> >
> > > If it *is* the same problem, what do you suppose is going to happen to
> > > those return values, if you try to execute this procedure in a script?
> >
> >I call this as execute procedure BEST_MATCOST (params) and it works fine,
> >from isql and via odbc and via ibadmin but not via database workbench
>
> So this really wasn't applicable to the problem?
>
> "When running the following script in the Script Editor of Database
> Workbench:
>
> execute procedure ABSENCE_RANGE (26,'10.01.2005','20.01.2005');
> execute procedure ABSENCE_RANGE2 (26,'10.01.2005','20.01.2005');
> execute procedure ABSENCE_RANGE_holjury (26,'10.01.2005','20.01.2005');
> execute procedure allowtime_RANGE (11,'10.01.2005','20.01.2005');
> execute procedure best_matcost (9,1.3);
> execute procedure best_matcost (10,10.3);
>
> I get this error:
> ..."
>
> ????
>
> I don't know DBWB but, presumably, there is a DSQL utility where you can
> test a procedure that returns values? A script isn't the right

environment

> for this...a script doesn't (can't) do anything with return values, so the
> XSQLVARs are left stuffed after the statement executes...

Right. That makes sense then. The Script Editor is using TIB_Script from
IBObjects.

As for the message - can I say "duh". What about a message that's a bit
more clear :-)

Either way, I'm trying to remember what this message means from now on :-)

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server
Upscene Productions
http://www.upscene.com