>-----Original Message-----
>From: Horodyski Marek (PZUZ) 
>Sent: Friday, September 11, 2009 10:22 AM
>To: Harbour Project Main Developer List.
>Subject: RE: [Harbour] Problems with ADORDD.
>
> 
>
>>-----Original Message-----
>>From: Ranier Vilela [mailto:[email protected]]
>>Sent: Thursday, September 10, 2009 10:02 PM
>>To: Harbour Project Main Developer List.
>>Subject: Re: [Harbour] Problems with ADORDD.
[...]
>>> oErr:subCode______      3012
>>> oErr:description__Nieprawidłowy argument // <-- wrong parameter 
>>> oErr:filename_____ oErr:operation____OPEN
>>> oErr:genCode______         1
>
>[...]   
>
>>Proballly ADORDD is broken because is ole intensive and ole 
>was changed 

I have access to Oracle via Microsoft ODBC :).
Failed Oracle-ODBC, but Microsofts work.

For all, try :
RDDINFO( 1001, { "ODBC", connectstring})

My connect string is :
"DSN=MyDescription;SERVER=TNSALIAS;PWD=PWD;UID=USER"

Where :
DSN=MyDescription is my name of record in ODBC table (with Microsoft driver).
SERVER=TNSALIAS   is alias from TNSNAMES.ORA file, where is described 
connection.
PWD is a password for user, 
UID is a user name in database.

And use via sqlmix :
DBUSEAREA( .T., "SQLMIX", "select * from ...", "MYALIAS")

ODBC is much much better than ADO. I have long names, numeric fields and 
timestamps :)
For examle :
DB struct: {{"PERSON_ID",            "N", 10,  0},
            {"EFFECTIVE_START_DATE", "@", 19,  0},
            {"EFFECTIVE_END_DATE",   "@", 19,  0},
            {"LAST_NAME",            "C", 150, 0},
            {"FIRST_NAME",           "C", 150, 0},
            {"MIDDLE_NAMES",         "C", 60,  0},
            {"FULL_NAME",            "C", 240, 0},
            {"START_DATE",           "@", 19,  0},
            {"DATE_OF_BIRTH",        "@", 19,  0},
            {"DATE_OF_DEATH",        "@", 19,  0},
            {"EMAIL_ADDRESS",        "C", 240, 0},
            {"EMPLOYEE_NUMBER",      "C", 30,  0},
            {"NARODOWOSC",           "C", 30,  0},
            {"PESEL",                "C", 30,  0},
            {"NIP",                  "C", 150, 0},
            {"SEX",                  "C", 30,  0},
            {"WORK_TELEPHONE",       "C", 4000,0},
            {"ADR_ULICA",            "C", 240, 0},
            {"ADR_NR_D",             "C", 240, 0},
            {"ADR_NR_L",             "C", 240, 0},
            {"ADR_MSC",              "C", 30,  0},
            {"KOD_POCZ",             "C", 30,  0},
            {"ADR_POCZTA",           "C", 120, 0},
            {"D_ADDRESS_TYPE",       "C", 80,  0},
            {"NAZWISKO_RODOWE",      "C", 150, 0},
            {"MSC_URODZENIA",        "C", 150, 0},
            {"IM_OJCA",              "C", 150, 0},
            {"IM_MATKI",             "C", 150, 0},
            {"OBYWATELSTWO",         "C", 150, 0},
            {"TYP_DOKUMENTU",        "C", 11,  0},
            {"NR_DOKUMENTU",         "C", 150, 0},
            {"ADR_DATE_FROM",        "@", 19,  0},
            {"ADR_DATA_TO",          "@", 19,  0},
            {"DATA_AKTUALIZACJI",    "@", 19,  0}}

ODBC correct queries database , where the ADO crashes.
And again I can work :)

Regards,
Marek Horodyski
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to