Re: Access, pass-through queries and isolation level

OK, I understand now. So this is really an Access issue.

As Jeff says:

>... Which is outside of the scope of what we normally do
>in Access... I suppose Philippe can reference
>psqlodbc.dll and issue the call in his VB code, but
>that is kind of nasty. Being able to transparently
>use SQL is the main attraction of a driver, at least
>for most of us.

I use Access for its great RAD features, so I'll try to solve my "isolation level" problems differently, for example by using a "lock table" inside the function. I wish there was a way to manage multiple result sets in Access more easily...

Thanks for your help, and of course, thanks for the ODBC driver!

Philippe

-----Message d'origine-----
De : Hiroshi Inoue [mailto:inoue(at)tpf(dot)co(dot)jp]
Envoyé : vendredi, 7. novembre 2003 22:57
À : Philippe Lang
Cc : 'Jeff Eckermann'; pgsql-odbc(at)postgresql(dot)org
Objet : RE: [ODBC] Access, pass-through queries and isolation level

> -----Original Message-----
> From: Philippe Lang
>
> Here we are...
>
> I understand more or less that the second query is not
> recognized as a select statement... That's apparently the
> reason why I cannot get the value back in Access.
>
> Are "multiple result sets" supposed to work with the ODBC driver?

Yes.
Psqlodbc driver returns 2 results for the query(SET ..;SELECT ..).
An SQLMoreResults call is needed to see the second result.

regards,
Hiroshi Inoue