Hummmm, not sure it is really related to a problem with ADORDD (see dos error).
I have exactly the same error trying to access Crystal report runtime XI.
Error occurred at: 01/12/2009, 14:26:32
Error description: (DOS Error -2147352567) OLE/3012 Argument error:
SETREPORTVARIABLEVALUE
Args:
[ 1] = C FADEVCUR
[ 2] = C True
Stack Calls
===========
Called from: => WIN_OLEAUTO:SETREPORTVARIABLEVALUE(0)
Called from: crwcole.prg => CRW:SETFORMULA(848)
I checked documentation at least 1 million time, arguments I send to
"SetReportVariableValue" are ok.
I suspect some argument type error in ole implementation.
Ole2TxtError() give DISP_E_EXCEPTION but I'm not sure it is related.
JF
-----Message d'origine-----
De : [email protected]
[mailto:[email protected]] De la part de Viktor Szakáts
Envoyé : mardi 1 décembre 2009 14:19
À : Harbour Project Main Developer List.
Objet : Re: [Harbour] Problem in OLE implementation
Hi Alex,
> USE test.mdb VIA "ADORDD" TABLE "Tabla1"
>
> with:
>
> USE xbrtest.mdb VIA "ADORDD" TABLE "Customer"
>
> it works. Perhaps test.mdb is broken?
Could be. Or it simply doesn't find it. But your
next example suggest that it's the former.
BTW: "broken", I've fixed this file at least once
already, and I'm sure it was working back then, so
maybe it's also possible that such .mdb files
aren't compatible with every db driver? I suspect
some hidden dependency here or IOW that .mdb isn't
a stable format, but more like .doc which tends to
break compatibility every now and then.
Fixing it looks to be futile to me, so I'm leaving
this to .mdb experts/users.
> access2.prg creates test2.mdb ok. On exiting it fails with:
>
> Error OLE/3012 Argument error: FIND (DOS Error -2147352567)
> Called from WIN_OLEAUTO:FIND(0)
> Called from ADO_LOCATE(1009)
> Called from __DBLOCATE(0)
> Called from MAIN(34)
>
> mysql1.prg :
>
> Error OLE/3012 Argument error: OPEN (DOS Error -2147352567)
> Called from WIN_OLEAUTO:OPEN(0)
> Called from ADO_OPEN(312)
> Called from DBUSEAREA(0)
> Called from MAIN(12)
>
> mysql.prg is the same except MAIN(14)
Thank you. So there still seem to be some things broken
after whichever update, my suspect is still the xhb sync job.
I see no point in moving it back to contrib until someone
takes a plunge into this and known problems get fixed.
[ The second one maybe just real open error, it's pointing
to some external service. ]
Brgds,
Viktor
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
