recorset.Filter question

recorset.Filter question

Post by Bill Wallac » Sat, 09 Mar 2002 18:51:43



Hi,

For some reason my brain is telling me that setting
a filter for a recordset causes a trip to the data source.
Is this correct or is my mind playing tricks on me again?

I Guess what I'm really asking is, on a small data base
(25 records, 20 fields) would it be better to get the whole
thing and use filters or get (7) seperate recordsets.

IIS4.0, MDAC 2.5, data source is on a different server than
the script.

Thnx,
Bill Wallace

 
 
 

recorset.Filter question

Post by Kalicanin Gora » Sat, 09 Mar 2002 19:36:44


Hi!

If you are using server side cursor then you are right and in such case
Filter property is not very effective.
If you are using client side cursor then everything is done on the client
and by my experience works fine.
You could even use some kind of index. There is a Dinamyc field property
'Optimize'.

Goran


Quote:> Hi,

> For some reason my brain is telling me that setting
> a filter for a recordset causes a trip to the data source.
> Is this correct or is my mind playing tricks on me again?

> I Guess what I'm really asking is, on a small data base
> (25 records, 20 fields) would it be better to get the whole
> thing and use filters or get (7) seperate recordsets.

> IIS4.0, MDAC 2.5, data source is on a different server than
> the script.

> Thnx,
> Bill Wallace


 
 
 

recorset.Filter question

Post by Bill Wallac » Sat, 09 Mar 2002 20:06:57


Thank you.  I this case I'm using a client side recordset.

Would filter work the same (or at all) server side if the
recordset was disconnected?

I had found the Optimize property and will play with it, it's a pretty small
recordset.

Thnx,
Bill Wallace


> Hi!

> If you are using server side cursor then you are right and in such case
> Filter property is not very effective.
> If you are using client side cursor then everything is done on the client
> and by my experience works fine.
> You could even use some kind of index. There is a Dinamyc field property
> 'Optimize'.

> Goran



> > Hi,

> > For some reason my brain is telling me that setting
> > a filter for a recordset causes a trip to the data source.
> > Is this correct or is my mind playing tricks on me again?

> > I Guess what I'm really asking is, on a small data base
> > (25 records, 20 fields) would it be better to get the whole
> > thing and use filters or get (7) seperate recordsets.

> > IIS4.0, MDAC 2.5, data source is on a different server than
> > the script.

> > Thnx,
> > Bill Wallace

 
 
 

recorset.Filter question

Post by Kalicanin Gora » Sat, 09 Mar 2002 20:39:20


Hi!

You can not have disconnected recordset with server side cursor.
Setting the cursor location to client side is important to get a
disconnected recordset.

Goran


> Thank you.  I this case I'm using a client side recordset.

> Would filter work the same (or at all) server side if the
> recordset was disconnected?

> I had found the Optimize property and will play with it, it's a pretty
small
> recordset.

> Thnx,
> Bill Wallace



> > Hi!

> > If you are using server side cursor then you are right and in such case
> > Filter property is not very effective.
> > If you are using client side cursor then everything is done on the
client
> > and by my experience works fine.
> > You could even use some kind of index. There is a Dinamyc field property
> > 'Optimize'.

> > Goran



> > > Hi,

> > > For some reason my brain is telling me that setting
> > > a filter for a recordset causes a trip to the data source.
> > > Is this correct or is my mind playing tricks on me again?

> > > I Guess what I'm really asking is, on a small data base
> > > (25 records, 20 fields) would it be better to get the whole
> > > thing and use filters or get (7) seperate recordsets.

> > > IIS4.0, MDAC 2.5, data source is on a different server than
> > > the script.

> > > Thnx,
> > > Bill Wallace