Ludek,
There is small problem apparently: if I replace
---
oCommand.Parameters.Append _
oCommand.CreateParameter("a", adInteger, adParamInputOutput, , a)
oCommand.Parameters.Append _
oCommand.CreateParameter("b", adInteger, adParamInputOutput, , b)
oCommand.Parameters.Append _
oCommand.CreateParameter("r1", adInteger, adParamOutput)
oCommand.Parameters.Append _
oCommand.CreateParameter("r2", adInteger, adParamOutput)
---
With
---
oCommand.Parameters.refresh
oCommand.Parameters("a").value = a
oCommand.Parameters("b").value = b
---
... MS Access crashes at the "oCommand.Parameters.refresh".
I have tried enabling MyLog, but nothing partularly interesting shows up in
there.
-----Message d'origine-----
De : Ludek Finstrle [mailto:luf@pzkagis.cz]
Envoyé : mardi, 25. avril 2006 18:38
À : Philippe Lang
Cc : pgsql-odbc@postgresql.org
Objet : Re: [ODBC] PG 8 INOUT parameters & ADO
> I have a PG 8.1.3 server with the following PL/PERL procedure:
>
> ------------
>
> CREATE FUNCTION perl_test(a inout integer, b inout integer, r1 out
> integer,
> r2 out integer) AS
...
> ------------
>
> I'm trying to call this procedure with ADO (latest version under XP),
> through the ODBC driver version 8.01.02.00, like this:
>
> ------------
>
> It fails, with error -2147217887 each time.
>
> Is it possible to query stored procedures like this with the PG ODBC
driver?
The psqlodbc 08.01.0200 doesn't support out parameters. Please try enhanced
experimental branch (07.03.026X) from pgfoundry.org.
This development branch is now CVS tip and it is the base for next stable
release (IMHO it is more stable then 08.01.0200).
Regards,
Luf
