ASP recordset filter failure

[Chris Oakleaf]

With the following code snippet:

<%="complexid =" & rsComplex("ComplexID")%>
<% rsPhoto.filter = "complexID =" & rsComplex("ComplexID") %>
<%response.Write("<br>ID: " & rsPhoto("complexID"))%>


I get an 80020009 error on the last line.

The first line appears in the HTML output as complex=589, so I know
that there is a valid value available for the filter.

This worked once and hasn't worked since.

The rsPhoto recordset is viewable in a seperate page. The complexID in
the associated table has a value of 561 in the complexID column.

Why would this fail?

Comments......
TIA

 

[Aaron [SQL Server MVP]]

You should apply this filter in your WHERE clause.

 

[Mark Schupp]

<%="complexid =" & rsComplex("ComplexID")%>

sb

<%"complexid =" & rsComplex("ComplexID")%>

 

[Chris Oakleaf]

Reply one submitted that I should not use .filter, but gave no reason
for not using a valid recordset method.

Reply two failed to realize that the first line of code posted the
filter sql string and is the equivalent of response.write.

Line two of the code is where the filter actually occurs.

Would anyone else have any comments.

*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

 

[Aaron [SQL Server MVP]]

Reply one submitted that I should not use .filter, but gave no reason

for not using a valid recordset method.

Reply two failed to realize that the first line of code posted the
filter sql string and is the equivalent of response.write.

What do you want for free? Shall we cook you lunch as well? Wipe your
mouth afterwards?

First, explain why ASP (which is processed ONCE) should go to the database,
get the whole table, send it all back over to ASP, so that you can say "oh,
wait, I only wanted these four rows." This is EXTREMELY wasteful!

Second, if you want us to properly evaluate the error, you might consider
posting the TEXT of the error message. I don't know how well your brain
works, but I haven't memorized every single error code and its corresponding
error message (never mind that many error codes, including the one you
posted, can have multiple error messages).

Third, if you did a search for 80020009 yourself, you might have found
possible reasons for the problem. Just because I didn't go out of my way to
explain why you shouldn't use "a valid recordset method" doesn't mean that
my advice is worthless. I also didn't go out of my way to explain why you
should avoid ADODB.Recordset because, like .filter, you don't need to use it
at all.

You might try being a little grateful for help that is being offered by
volunteers, instead of being snotty about how miserably we failed you.