Subject | Re: [IBO] Re: CURRENT_USER Failure |
---|---|
Author | Helen Borrie |
Post date | 2008-12-17T11:49:17Z |
At 09:29 PM 17/12/2008, you wrote:
Helen
>I use madExcept for error trapping and reporting. I can forward itsNo thanks. Put an ib_monitor onto your mainform and trace the statement going over the wire and the exception that comes back. Copy/paste the relevant part of the API trace.
>report if that would be quickest. Other than that I can take screen
>dumps.
>Bottom line is exception class EIBO_EISCError, exceptionHmm. Can't help if you don't provide *something* that's relevant to IBO and Firebird. Are you sure you're not running an InterBase server 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.
>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.
Helen