21
Replies
Thanks! This is so much common sense.
I still have the other larger issue where the selection criteria requires interrogating the form variables to see if they are set or not, and the one set of checkboxes that can have multiple values set requiring me to build an "or" in the where clause potentially with several "and" conditions. This code is working fine as it is, but now that I'm getting more data in my db, I want to provide page navigation through the results set.
Incorporating the page navigation in the results set has introduced an even larger issue that I've posted in another discussion thread. When the next page is selected, the code re-executes the mysql select, but the form variables have been reset and the second page executes a select that retrieves every record in the db. I'm not clear how to prevent resetting the form variables so that my results are consistent when paging through the results set.
This is sweet! I have modified the code as you suggested and it is much shorter, but more difficult for my novice brain to comprehend.
I'm having a bit of trouble with the results.
If I select color = fawn and search, I expect 2 pages of dogs with 10 on the first page. I've got echo statements in there to keep track of variables. Here are their values when the first page displays:
formStatus = submitted
submitted search criteria for session = a:4:{s:9:"s_color_f";s:1:"f";s:6:"button";s:6:"Search";s:10:"formStatus";s:9:"submitted";s:8:"redirect";s:14:"danequest.html";}
where = Array
query_rs_results = SELECT dogid, b_email, b_fname, b_lname, b_phone, b_url, dob, dod, reg_name, reg_no, o_email, o_fname, o_lname, o_phone, o_url, registry,semen_l, semen_f, semen_fc, semen_fr, photo FROM dog_main WHERE color IN ('f')
query_limit_rs_results = SELECT dogid, b_email, b_fname, b_lname, b_phone, b_url, dob, dod, reg_name, reg_no, o_email, o_fname, o_lname, o_phone, o_url, registry,semen_l, semen_f, semen_fc, semen_fr, photo FROM dog_main WHERE color IN ('f') LIMIT 0, 10
row_rs_results = Array
totalPages_rs_results = 2
So the code you gave me to shorten building the where clause is working very nicely!
When I click "next" to go to page 2, I have once again lost my where condition and all records in the db are retrieved. Here are the values in the variables:
formStatus =
else search criteria for session =
where =
query_rs_results = SELECT dogid, b_email, b_fname, b_lname, b_phone, b_url, dob, dod, reg_name, reg_no, o_email, o_fname, o_lname, o_phone, o_url, registry,semen_l, semen_f, semen_fc, semen_fr, photo FROM dog_main
query_limit_rs_results = SELECT dogid, b_email, b_fname, b_lname, b_phone, b_url, dob, dod, reg_name, reg_no, o_email, o_fname, o_lname, o_phone, o_url, registry,semen_l, semen_f, semen_fc, semen_fr, photo FROM dog_main LIMIT 0, 10
row_rs_results = Array
totalPages_rs_results = 5
This is the same thing that was happening before. All form variables are reset on the second select statement and I've lost my criteria and all dogs in the db are selected. It looks like it is resetting the session variables too. 
What is also happening is that, no matter what my selection critieria is, the first page has the correct dogs displayed. But, instead of starting with the 11th dog in the selected records on the second page, the first dog in the db is at the top of the page and every page there after starts with the first dog in the db and shows the same 10 dogs. So it is not setting the start row for the next page correctly.
I need to let this soak into my brain a bit. After it marinates for a while I'll figure out what to try next and post again.
Hello Dane & Nate,
Thanks for the pieces of code examples to get complex selection queries working!
I have a question however. I'm a beginner with Dreamweaver.
My problem is: everytime a make modifications in the (generated) code of my application
red exclamation points appear in the server behaviour panel. (and I cannot get rid of them )
Is that a problem? What should I do about this behaviour? Or is this normal?
I cannot edit the server behavior nor can I create a new one.
My application is an application to search in a bibliography presenting a window with a list (grid) with records and a navigator. Users can use a form
with some fields in which they can enter selection criteria.
After submitting the form I build the (complex) selection criterium and push that into the recordset selector.
So I have to modify the generated recordset server behaviour (in the code).
Hope I'm clear.
Thanks,
LexvS
I've got it working. I took the new & improved where clause and added a session_start() before the "submitted" test , then combined it with the pagination code I had originally and voila, it works.
Thanks for all your generous assistance!
The next improvement will be to display the number of records retrieved with a default of 10 per page and allow the user to select the number of records per page to display.
AdChoices