Subject | Re: [firebird-support] Problems with UDF access |
---|---|
Author | Jason Dodson |
Post date | 2005-12-22T15:45:21Z |
Which brings light to the need for less ambiguous error messages.
Jason
Pavel Menshchikov wrote:
The information transmitted herewith is sensitive information intended only for use to the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon, this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
Jason
Pavel Menshchikov wrote:
> Hello,--
>
> PM> I didn't develop using FB a number of monthes. Now on a new notebook I
> PM> have WinXP Pro SP2, FB 1.5.2 (SS running as a service, and embedded,
> PM> both with default firebird.conf). I have an SQL script that runs in my
> PM> Delphi program via FIBScript (which uses FIB+ components) and creates
> PM> a database. The error occures in a stored procedure that refer to a
> PM> UDF (declared above in the same script) - FB says
> PM> -----
> PM> Invalid token.
> PM> invalid request BLR at offset 2606.
> PM> function ACMIN is not defined.
> PM> module name or entrypoint could not be found.
> PM> -----
>
> For your information: the problem was with using msvcrt's malloc
> function in my UDF library. Probably, an issue with the msvcrt.dll
> versions... - I have those files in a number of places, including
> windows\system32 folder. After rebuilding UDF library with ib_util's
> ib_util_malloc function, UDF works fine.
>
>
The information transmitted herewith is sensitive information intended only for use to the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon, this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.