Recent content by altink

Thank You very much Mr. Kalter For sure I will buy and upgrade to DOA 4.1.4. Can't think of working Delphi->Oracle without it. Same for PL/SQL Developer. Keep the great job best regards Altin

Hi When I try to connect with an Oracle 11g R2 Classic Client to an Oracle 19c DB, with both: PL/SQL Developer 11.0.4 DOA Runtime (Design-time - Delphi TOracleSession) 4.1.3.5 - Delphi 10.1 Berlin I get error ORA-28040: No matching authentication protocol (which can be fixed DB-side by adding...

Thank You very much Mr. Kalter One last question: Does DOA 4.1.4 supports Oracle 10g release 2 ? best regards Altin

Thank You Mr. Kalter Is DOA 4.1.4 a stable version? Asking because on product pagehttps://www.allroundautomations.com/products/direct-oracle-access/ ... under "System requirements", I read: "The supported Oracle Server versions are 7.x, 8.x, 8i, 9i, 10g, 11g, 12c, 18c and 19c on any...

Hello I do use a registered DOA version in my Delphi application, and do experience errors with Oracle 21. Error 1: : Type mismatch for field '', expecting DateTime actual: WideString The is a TIMESTAMP(6) in a table that also has three CLOB fields. Happens when I query from my Delphi...

Hello, I made use of TOracleSession.TimestampAsString:=True and in an TOracle Dataset tried: select SYSTIMESTAMP as timestamp_sts from dual and got the timestamp as widestring. The problem is that it comes in format: 12-JAN-18 10.26.23.350000 PM +01:00 Is there any way to control the format...

Thank you Marco the same persistent field conversion should also be: TMemoField -> TWideMemoField in this case there will be no errors, just a non-working display of characters. I am looking for any other string-related field conversion thanks and regards Altin

Thank you very much Marco I did the test and it worked. As far as I saw it this (TStringField->TWideStringField) was a common solution in this case, not only for DOA components, but in general. My fear is (and sorry for my superficial knowledge): Since now and one both Western and Unicode will...

correction: 2. Session's ForceWideStringFields is set True so that the DOA datasets "percieves" all VARCHAR2(x) as TWideStringFields and not TStringFields no matter when DB is WE8MSWIN1252 or AL32UTF8

Thank you very much Marco. Please let me summarize: In an existing DOA project, built with TOracleDatasets with persistent TStringFields on VARCHAR2(x) columns, into a WE8MSWIN1252 Oracle DB; the only way to have the project compliant with both Western Languages and Unicode is like in the...

Hi Marco Clarification: I did access the WE8MSWIN1252 database with TOracleSession.Preferences.ForceWideStringFields = False I used ForceWideStringFields=True in case of AL32UTF8 DB - but no result. If I use ForceWideStringFields=True, even with a WE8MSWIN1252 I get the error...

The TOracleSession.Preferences.ForceWideStringFields property is already set to True, as put above, and it didn't made a difference in my error, it comes out the same. Please advise thanks and regards Altin

Hello I have a TOracleDataset bound to a TOracleSession, connected to an Oracle 11g R2 database with: NLS_LANGUAGE=AMERICAN NLS_CHARACTERSET=WE8MSWIN1252 The NLS_LANG environment variable on the client is set to AMERICAN_AMERICA.WE8MSWIN1252. The OracleDataset has declared String fields from...

Thank You Mr. Kalter But I need to use a DBGrid on the result. What about PL/SQL ? Does it make use of TOracleDataset ? I can query same amount of data with that. I have seen that it has a functionality to fetch records Next N records (like in the web) or All. Any workaround on this ? Thanks...

It is a select command. What do you mean by DDL table ?