odbc recordset.open with adCmdTable gets entire table on call

odbc recordset.open with adCmdTable gets entire table on call

am 27.01.2006 14:41:10 von Antoine

------=_Part_40759_30511185.1138369270681
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,
I have figured out the problem to the network overload looking at the
queries via ethereal.
The problem is this:

prec_recordset.open "my_table", my_connection, adOpenStatic,
adLockOptimistic, adCmdTable

returns, as the msdn suggests it should the ENTIRE table. Or does it? With
Oracle we have been using this instruction and it doesn't return the data
for the entire table - in fact I don't think it returns very much at all. I=
s
there a parameter we are missing on our connection string?
Cheers
Antoine

--
This is where I should put some witty comment.

------=_Part_40759_30511185.1138369270681
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,
I have figured out the problem to the network overload looking at th=
e queries via ethereal.
The problem is this:

prec_recordset.open =
"my_table", my_connection, adOpenStatic, adLockOptimistic, adCmdT=
able


returns, as the msdn suggests it should the ENTIRE ta=
ble. Or does it? With Oracle we have been using this instruction and it doe=
sn't return the data for the entire table - in fact I don't think it return=
s very much at all. Is there a parameter we are missing on our connection s=
tring?

Cheers
Antoine

--
This is where I should put some witty c=
omment.

------=_Part_40759_30511185.1138369270681--

Re: odbc recordset.open with adCmdTable gets entire table on call

am 27.01.2006 15:19:00 von Ludek Finstrle

> prec_recordset.open "my_table", my_connection, adOpenStatic,
> adLockOptimistic, adCmdTable
>
> returns, as the msdn suggests it should the ENTIRE table. Or does it? With
> Oracle we have been using this instruction and it doesn't return the data
> for the entire table - in fact I don't think it returns very much at all. Is
> there a parameter we are missing on our connection string?

There is use declare/fetch option which I mentioned few seconds ago
in another e-mail to you :-)

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq