Re: Cannot open Access table with ADO or BDE/ODBC
- From: "Doug Stephens" <dougstephens@xxxxxxxxxx>
- Date: 19 May 2006 10:32:48 -0700
In ADO whether all records
fetched in memory or not is controlled by Cursor Location property
and doesn't depend on DB backend at all.
Works fast with clUseServer. What are the tradeoffs here? From my
little testing I can see no disadvantages to keeping cursor (resultset)
on the server. Grid populates fast. Open is fast. Why would anyone use
a client side cursor?
This is only available in ADO, right? Would be nice if I could do that
with BDE. Does BDE then use a client side cursor, i.e. copy all the
data to client when I do table.open? (I'm stuck with a large BDE app
right now)
.
- Follow-Ups:
- Re: Cannot open Access table with ADO or BDE/ODBC
- From: Vitali Kalinin
- Re: Cannot open Access table with ADO or BDE/ODBC
- References:
- Cannot open Access table with ADO or BDE/ODBC
- From: Doug Stephens
- Re: Cannot open Access table with ADO or BDE/ODBC
- From: Vitali Kalinin
- Re: Cannot open Access table with ADO or BDE/ODBC
- From: Doug Stephens
- Re: Cannot open Access table with ADO or BDE/ODBC
- From: Vitali Kalinin
- Re: Cannot open Access table with ADO or BDE/ODBC
- From: Doug Stephens
- Re: Cannot open Access table with ADO or BDE/ODBC
- From: Guillem
- Re: Cannot open Access table with ADO or BDE/ODBC
- From: Vitali Kalinin
- Cannot open Access table with ADO or BDE/ODBC
- Prev by Date: Prompt DataSource Causes CPU window to appear
- Next by Date: Re: Red squigglies in D2006
- Previous by thread: Re: Cannot open Access table with ADO or BDE/ODBC
- Next by thread: Re: Cannot open Access table with ADO or BDE/ODBC
- Index(es):
Relevant Pages
|