 |  |  |  |  |  |  |  |
ASP vbscript recordset paging headache
Please support our ASP advertiser: PostgreSQL or MySQL? Compare and contrast the two most popular open source databases
 |
Hi,
I am having a problem using Dreamweaver CS3 standard recordset paging behavior. It doesn’t seem to work when I pass parameter values from a FORM on my search page, to the recordset on my results page.
- Recordset Paging works if no parameters are used in the recordset sql code (ie. simple sql code):
SELECT *
FROM db_name
WHERE (db_field1 LIKE ‘%text1%’ OR db_field2 LIKE ‘%text2%’)
- Recordset Paging works if I pass the same text to the sql code using parameters set within the recordset:
SELECT *
FROM db_name
WHERE (db_field1 LIKE %parameter1% OR db_field2 LIKE %parameter2%)
--> inside the recordset parameter1 was set to ‘text1’, parameter2 was set to ‘text2
- However if I pass the same text (text1, text2) from a FORM on a search page to the recordset using recordset parameters, the Recordset Paging fails.
SELECT *
FROM db_name
WHERE (db_field1 LIKE %parameter1% OR db_field2 LIKE %parameter2%)
--> inside the recordset parameter1 and parameter2 were set using the Request.Form("….")
--> on the FORM the values of the fields were set to text1, text2
The form, database, sql code all work fine. After I perform a search, the correct database results are displayed on my first results.asp page. My problem is when I try to use recordset paging. For some reason when I try to page through the results I get the following error:
Error Type:
ADODB.Field (0x800A0BCD)
Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.
I have completely striped my code to the bare essentials, and conclude that the search criteria are not being sent to the results page each time I click “Next” etc. Therefore each time I try to page through the results, the recordset values are all empty and the EOF value is returned.
Please have a quick look at the code below. Any help, advice, suggestions or other scripts (javascript or vbscript) that will work instead will be gratefully accepted. I have been trying to fix this for days and it’s driving me crazy.
To help you understand the code here is a brief explanation of its purpose, a list of the variables used and the error produced.
- takes 2 search fields from FORM on search page (SearchValue1 = city, SearchValue2 = country)
- compares with database field (Keywords) for any matches (database name = test20.mdb)
- outputs the text contents of database field (Image_Name)
- the text outputs are displayed one per page eg. page 1 = record 1, page2 = record 2, page 3 = record 3 ....
- a "Next" link pages through the displayed results
File Name = results.asp
Connection File Name = con_cwphoto.asp
Recordset Name = rs
Database name = test20.mdb
Database Field Names = Keywords, Image_Name
FORM Fields (on search.asp page) = SearchValue1 (city), SearchValue2 (country)
The URL passed by clicking the “Next” link:
http://localhost/conor%20wall%20phot...Submit&index=1
It seems to pass the search criteria, but maybe it isn’t being passed correctly.
The error:
Error Type:
ADODB.Field (0x800A0BCD)
Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.
The line the error points to:
This line is in the html tags and displays the contents of the “Image_Name” database field.
The CS3 recordset paging behavior code:
I am having a problem using Dreamweaver CS3 standard recordset paging behavior. It doesn’t seem to work when I pass parameter values from a FORM on my search page, to the recordset on my results page.
- Recordset Paging works if no parameters are used in the recordset sql code (ie. simple sql code):
SELECT *
FROM db_name
WHERE (db_field1 LIKE ‘%text1%’ OR db_field2 LIKE ‘%text2%’)
- Recordset Paging works if I pass the same text to the sql code using parameters set within the recordset:
SELECT *
FROM db_name
WHERE (db_field1 LIKE %parameter1% OR db_field2 LIKE %parameter2%)
--> inside the recordset parameter1 was set to ‘text1’, parameter2 was set to ‘text2
- However if I pass the same text (text1, text2) from a FORM on a search page to the recordset using recordset parameters, the Recordset Paging fails.
SELECT *
FROM db_name
WHERE (db_field1 LIKE %parameter1% OR db_field2 LIKE %parameter2%)
--> inside the recordset parameter1 and parameter2 were set using the Request.Form("….")
--> on the FORM the values of the fields were set to text1, text2
The form, database, sql code all work fine. After I perform a search, the correct database results are displayed on my first results.asp page. My problem is when I try to use recordset paging. For some reason when I try to page through the results I get the following error:
Error Type:
ADODB.Field (0x800A0BCD)
Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.
I have completely striped my code to the bare essentials, and conclude that the search criteria are not being sent to the results page each time I click “Next” etc. Therefore each time I try to page through the results, the recordset values are all empty and the EOF value is returned.
Please have a quick look at the code below. Any help, advice, suggestions or other scripts (javascript or vbscript) that will work instead will be gratefully accepted. I have been trying to fix this for days and it’s driving me crazy.
To help you understand the code here is a brief explanation of its purpose, a list of the variables used and the error produced.
- takes 2 search fields from FORM on search page (SearchValue1 = city, SearchValue2 = country)
- compares with database field (Keywords) for any matches (database name = test20.mdb)
- outputs the text contents of database field (Image_Name)
- the text outputs are displayed one per page eg. page 1 = record 1, page2 = record 2, page 3 = record 3 ....
- a "Next" link pages through the displayed results
File Name = results.asp
Connection File Name = con_cwphoto.asp
Recordset Name = rs
Database name = test20.mdb
Database Field Names = Keywords, Image_Name
FORM Fields (on search.asp page) = SearchValue1 (city), SearchValue2 (country)
The URL passed by clicking the “Next” link:
http://localhost/conor%20wall%20phot...Submit&index=1
It seems to pass the search criteria, but maybe it isn’t being passed correctly.
The error:
Error Type:
ADODB.Field (0x800A0BCD)
Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.
The line the error points to:
ASP Syntax (Toggle Plain Text)
This line is in the html tags and displays the contents of the “Image_Name” database field.
The CS3 recordset paging behavior code:
ASP Syntax (Toggle Plain Text)
•
•
Join Date: Sep 2007
Posts: 1,080
Reputation: 
Solved Threads: 68
First try to add the parameters directly into the query string. If that works (which it should) it is within your parameter code. I never used parameter coding with classic asp. I instead set up a little function that stripped it of all harmful words and characters, then placed it directly in.
Hi,
Thanks for the reply. The query string that is being passed each time I click the “Next” link is shown below:
http://localhost/...../results.asp?S...Submit&index=1
This SEEMS to pass the parameters. Does this string look okay to you? Maybe it has not been pieced together correctly?
Thanks again,
Conor
Thanks for the reply. The query string that is being passed each time I click the “Next” link is shown below:
http://localhost/...../results.asp?S...Submit&index=1
This SEEMS to pass the parameters. Does this string look okay to you? Maybe it has not been pieced together correctly?
Thanks again,
Conor
That query string came out looking like an active link in the last post. Hopefully this time it shouls look clearer.
://localhost/...../results.asp?SearchValue1=city&SearchValue2=country&submit=Submit&index=1
://localhost/...../results.asp?SearchValue1=city&SearchValue2=country&submit=Submit&index=1
Hi,
Following the suggestion of a member of a different forum, I have fixed the code error.
The code which gets the search values from the FORM on the search page, must be changed so that it also gets the search values passed in the URL query string. Only one of these occurrences will ever happen. The first time the results.asp page is displayed it will use the search values pulled from the FORM. All other times the results.asp page is displayed (because of recordset paging - Next, Previous …) it will use the same search values, but this time pulled from the URL.
Therefore the code:
Must be changed to:
I will also email Dreamweaver to tell them to update their standard record paging behavior code. Thanks to all who replied with help.
Conor
Following the suggestion of a member of a different forum, I have fixed the code error.
The code which gets the search values from the FORM on the search page, must be changed so that it also gets the search values passed in the URL query string. Only one of these occurrences will ever happen. The first time the results.asp page is displayed it will use the search values pulled from the FORM. All other times the results.asp page is displayed (because of recordset paging - Next, Previous …) it will use the same search values, but this time pulled from the URL.
Therefore the code:
ASP Syntax (Toggle Plain Text)
Must be changed to:
ASP Syntax (Toggle Plain Text)
I will also email Dreamweaver to tell them to update their standard record paging behavior code. Thanks to all who replied with help.
Conor
•
•
Join Date: Sep 2007
Posts: 1,080
Reputation:
Solved Threads: 68
You should do your best to keep it consistent, searching only one the querystring or form. It won't matter, really, it won't, but I am picky and keep things consistent!
I would just remove the form value and pull from the querystring. Also, you should set up an "only integer" function that will eliminate any characters taht aren't integers. This works well with keeping errors low when people screw with url's. To see what I mean, try typing in something else but an integer in your paging portion of the url.
I would just remove the form value and pull from the querystring. Also, you should set up an "only integer" function that will eliminate any characters taht aren't integers. This works well with keeping errors low when people screw with url's. To see what I mean, try typing in something else but an integer in your paging portion of the url.
|
Other Threads in the ASP Forum
- Previous Thread: global.asa explaination
- Next Thread: Problem in inserting data to the database
| Thread Tools | Search this Thread |
You need to join our community in order to build your list of favorite forums. You can visit the forum index for a listing of all forums.
Related Forum Features
Latest ASP Posts
- Today's Posts
- Unanswered Threads
archive asp asp.net aspandmssqlserver2005 aspandmssqlserver2005connection aspconnection connection database databaseconnection dreamweaver excel fso iis msmsql mssql2005 mssqlserver2005 mssqlserver2005andasp mssqlserverandasp opentextfile record searchbox selectoption single specfic sqlserver sqlserverconnection windows7
