Subject | Re: CURRENT_USER Failure |
---|---|
Author | george.elton197 |
Post date | 2008-12-17T14:33:42Z |
--- In IBObjects@yahoogroups.com, Helen Borrie <helebor@...> wrote:
Copy/paste the relevant part of the API trace.
there? Firebird had CURRENT_USER from v.1.5 onwards. There's no
reason why Firebird would barf on it. Sounds more like IB running
there and using IB's message file...or maybe Fb 1.0.x and *its* msg file.
Yep, no IB here, just Firebird. This is a clean pc, little else on it.
I'll do as you suggest.
Thanks again.
>statement going over the wire and the exception that comes back.
> At 09:29 PM 17/12/2008, you wrote:
>
> >I use madExcept for error trapping and reporting. I can forward its
> >report if that would be quickest. Other than that I can take screen
> >dumps.
>
> No thanks. Put an ib_monitor onto your mainform and trace the
Copy/paste the relevant part of the API trace.
>IBO and Firebird. Are you sure you're not running an InterBase server
> >Bottom line is exception class EIBO_EISCError, exception
> >message Unknown. If I remove CURRENT_USER from the SQL select it works
> >fine (well, apart from returning what I don't need).
> >
> >Again, thanks for your help.
>
> Hmm. Can't help if you don't provide *something* that's relevant to
there? Firebird had CURRENT_USER from v.1.5 onwards. There's no
reason why Firebird would barf on it. Sounds more like IB running
there and using IB's message file...or maybe Fb 1.0.x and *its* msg file.
>Helen
> Helen
>
Yep, no IB here, just Firebird. This is a clean pc, little else on it.
I'll do as you suggest.
Thanks again.