Recent content by koadam

Hi! No, it doesn't work. The error is the same: "invalid argument to date encode". I think this is somehow connected with the OCI api, and maybe the server's/client's nls settings. My computer is configured in windows as "hungarian region". My oracle's nls_lang is...

ok, i sent it again a few days before. Did you receive it? What mail address should I use? I sent to address "support@" K.

Hi, I tried it with latest doa version, and it gives the same results (AV). If I change type "tocidate" to "TDatetime" gives also errors (parameter stack overflow, or something like this). Please help me to get this thing to work. Thanks in advance, Koadam

Hi, I sent a test project to the support@allround... address. Please check it. I hope it helps. B.

ok, that was my mistake when I prepared the sample codes. Correcting the mistakes, the ocidatefrom... still does not work. DOA 3.4.6 is ok for this feature? B.

Hi, A'm also interested in the above question. I want to write the external function/procedure with doa, returning a cursor. The client-side will be delphi applications using DOA and ODAC components. B.

Hi, thanks for your answer. The code snippets from the est dll code is: var Func1Result: TOCINumber = nil; function XXX_TEST2(Context: Pointer; ADateLo, ADateHi: TOciDate; ACards: PChar; AIntParam: TOciNumber): PChar; cdecl; var dLo, dHi: TDateTime; i: integer; begin Result:=nil...

Hi, we have doa 3.4.6.1. We try to write external funcions for oracle 8.1.7. My delphi func header looks like: function TEST(Context: Pointer; dLo, dHi: TOciDate; i: integer): integer; cdecl; I try to convert ocidate to delphi datetime with: Session.ExtProcShare(Context)...

Hi, All of our programs (using doa) show an errorbox with message "the ordinal 435 could not be located in the dynamic link library core40.dll". After the errorbox the application starts and works without any error. Is there any solution to eliminate this unnecessary error? Koadam

yes, that right. But, The problem is that you can add field only to a closed/inactive dataset. So, before opening the query I know nothing about the fields after opening.

yes, it works. **But if you look at your dbgrid, the only field shown in the grid is the "blabla" field. That's my problem

Hi, Can someone show me how can I create a calculated field at runtime with a TOracleDataSet? The sql is constructed also at runtime, so I *have to create the calc field at runtime, too. I tried the following code: f:=TIntegerField.Create(ods1); f.FieldName:='blabla'; f.FieldKind:=fkCalculated...