Can i use filter property like in Access 2000?!?

Question

Can i use filter property like in Access 2000?!?

GENKO

SSC Veteran

Points: 218
More actions
July 9, 2003 at 1:23 am

#160518

Hi, i've build a site with asp and access 2000 db, i've used a lot off filter for update and extracting record from my tables.
Now i'm going to think to convert it in sql server, and my trouble is.....can i maintain the filter like in access 2000!?!?

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Frank Kalis SSC Guru Points: 111183 More actions · Answer 1

Hi GENKO,

quote:
Hi, i've build a site with asp and access 2000 db, i've used a lot off filter for update and extracting record from my tables.
Now i'm going to think to convert it in sql server, and my trouble is.....can i maintain the filter like in access 2000!?!?

if you mean whether you can still use the ADO filter property, the answer is YES.

I am not sure, if filtering occurs on the server or the client, so it might be better to use a SELECT statement with an appropriate WHERE clause.

Maybe someone else knows where filtering is done?

Cheers,

Frank

--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

GENKO SSC Veteran Points: 218 More actions · Answer 2

a5xo3z1, thank for the answer, my script in asp are server side for accessing db, so i think it'll be the same for sql server, or no??

i know that its better the sql string anywhere but in my site there is an alternate type of access, sometimes i need string sql and sometimes i prefer use the filter property...

i'm testing my site offline using pws.

Edited by - GENKO on 07/09/2003 02:15:43 AM

contactanwar SSC Enthusiast Points: 153 More actions · Answer 3

The problem with filter is you have to select too much data in initially to begin with. This isn't so much a problem with access as it pulls in extra data anyway being file based. But with SQL Server you don't want to pull in unnecessary data. For instance, imagine if I have a client table and only want one client. If I want to use an ADO filter then I will have to pull all client records into the server's memory and then apply a filter. With an SQL Select statement I let the SQL Server do what it was built for. The filter can be good if you have a recordset that you want to reuse to constantly lookup records (clients in this case).