If you want to use all of the features recordsets offset the
only way is to use adUseClient (in particular to update a
recordset, I guess, since updatable recordsets are a new
feature of the odbc driver and maybe not fully stable too).
I use exclusively adUseClient connections and I'm fine with
it... and I'm pretty sure that many other people has code
that relies only on adUseClient connection, so it should be
"Corey W. Gibbs" wrote:
> Good Morning Everyone (or evening as the case may be),
> Just a quick question about the cursor location property of an ADO
> recordset object.
> adUseServer is the default, has anyone ever switched it to adUseClient to
> use the .Sort and .Filter methods of the ADO recordset? I am helping
> another programmer convert an application that uses Access datafile to PG.
> I've always just left it adUseServer and wrote various SQL statements to
> fill my recordsets, but he has extensive use of .Sort and .Filter in his
> I've checked out some websites and they all say that adUseServer is a real
> resource hog on the server, but that's fine with me because the DB is on a
> slick machine. Can anyone offer any advice?
> thanks in advance
> Corey W. Gibbs
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
In response to
pgsql-odbc by date
|Next:||From: Francisco Jr.||Date: 2002-05-12 01:40:38|
|Subject: [ANN] Npgsql .Net Data Provider Project Launch!|
|Previous:||From: Hiroshi Inoue||Date: 2002-05-10 05:11:21|
|Subject: Re: Individual subsystems' CVS tags?|