I'm using version 4.3.Aa of IBO and Interbase 6.0 with a gds32.dll
version of 6.2.0.794.

What is even stranger is that I only get the message length error on
Window Nt 4.0 or Windows 2000 server but not on Windows XP Pro. All
using the same IBO and GDS version.

Thanks,

Matt

--- In IBObjects@yahoogroups.com, Helen Borrie <helebor@t...> wrote:
> At 11:17 PM 17/02/2004 +0000, you wrote:
> >Are there any known issues using Stored Procedures inside a
TService
> >type application? I have a TIB_Session object and am using a
> >TIB_Connecion that my TIBOStoredProcedure is attached to and it
fails
> >with a message length error just about every time when I run the
> >service on NT 4.0 and most of the time on Windows 2000 server, but
if
> >I run it on Windows XP it seems to work fine.
> >
> >Very strange. I've moved away from using the stored proc's in my
> >service and I think It will work out but I just wanted to know if
> >anyone else has had the same problem or maybe I'm not connecting my
> >session and connection objects correctly.
>
> That message length error is the one you get when you try to
SELECT from a
> SP that should be executed, or EXECUTE a SP that should be
SELECTed. Have
> you eliminated that possibility?
>
> It can also be the one you see with the XSQLDA bug. What versions
of IBO
> and database server are you using?
>
> As to not using SPs in a service - that is ridiculous. Using a
storedproc
> object for an executable SP could be a factor - I use TIB_DSQL for
them as
> a matter of course. It is thinner and gets absolutely to the heart
of the
> task, without all that TField and buffering overhead.
>
> Helen