On Thu, 13 Mar 2014 14:33:19 -0300, Weverton Gomes wever...@gmail.com
wrote:
Hi,
I have just started testing FB 3.0 Alpha 2 (32 bits) and I'm getting in
trouble using the same UDF's I already use in FB 2.5. I'm getting the
known
message:
Invalid token.
invalid request BLR at offset 35.
Alex, the dll file is available at http://www.sendspace.com/file/02v4af
Vlad, this dll was compiled in Delphi. So, I think there is no dependencies.
Mark, I put the ? as a wildcard; in this space came the UDF name (e.g.
UDF_MAX).
Thank you all,
Weverton Gomes de Morais
Tecnólogo em Redes de
14.03.2014 16:43, Weverton Gomes wrote:
the dll file is available at http://www.sendspace.com/file/02v4af
Do you suggest him to decompile your DLL? Show sources of your UDF_MAX.
this dll was compiled in Delphi. So, I think there is no dependencies.
Thinking is not enough. Your DLL may
14.03.2014 17:01, Weverton Gomes wrote:
It uses only simple structures to work with strings, numbers and dates.
Dates? Do you really work with ISC_TIMESTAMP without calling
isc_decode_timestamp()???
--
WBR, SD.
DSDates? Do you really work with ISC_TIMESTAMP without calling
isc_decode_timestamp()???
It is not difficult to decode/encode ISC_TIMESTAMP using pure pascal
;) Just basic math with some divs and mods...
[]s
Carlos
http://www.firebirdnews.org
FireBase - http://www.FireBase.com.br
DS
Yes. The source use a pointer to a delphi structure to represent the
timestamp. And, as I said before, this works normally since FB 1.5.
TFBDate = integer;
TFBTime = Cardinal;
{ FireBird TimeStamp record }
TFBTS = packed record
Date: TFBDate;
Time: TFBTime;
end;
PFBTS =
14.03.2014 17:45, Weverton Gomes wrote:
Yes. The source use a pointer to a delphi structure to represent the
timestamp. And, as I
said before, this works normally since FB 1.5.
For me it works with 3.0 as well:
SQL declare external function ate timestamp returns smallint by value
