Posted: 30 October 2009 at 3:54pm | IP Logged

Can someone please tell me why I can only navigate through my record set if the query doesn't contain parameters?  When I pass parameters via a search form,  my records will display.  But, when I click my navigation button "Next" , I get an error message telling me that "element fishfamily is undefined".  I tried caching the query results hoping that I would be able to scroll though the record set without resending the query.  It appears to me that this is not happening, and that when I click the "Next" button, the query is resubmtted.  Since "fishfamily" is an empty parameter, the query bombs.

Help is appreciated!!!

Here's my code: (Look at the file attached to my December posting for this code along with the solution.)

Posted: 05 November 2009 at 2:30pm | IP Logged

Thanks Siew,

I'm not passing any url parameters.  The values are passed by the calling form by means of form fields:

<cfform action="the_paging_page.cfm" datasource="stuff">

<select name="fishfamily">
        <option value="">-- list --      <cfoutput query="getfamily">
<!---<option value="#getfamily.family#">#lcase(getfamily.family)#  ;     </cfoutput>--->
<option value="#getfamily.family#">#getfamily.family#       </cfoutput>
      </select>

It seems that I somehow need to capture the values from the calling page so that they can be resued by the action page. 

Posted: 08 November 2009 at 3:18pm | IP Logged

You have this

<cfif form.fishfamily neq "">

            and family = '#form.fishfamily#'

            </cfif>

so form.fishfamily must exist.

If you are clicking a link, then the form is not submitted so u get an error.

if you want to use both form and url then you need to make sure all the variables exist in both scopes. Or simply stick to using only forms. When clicking a page link, you can use javascript to pass the page number into a hidden field and then submit the form.

Remember that not scoping your variables means that cf will search all scopes, which is one way to use both form or url, but could result in values being pulled from another scope. Another alternative is to copy the form and url into a custom scope and use that instead. This is how fusebox used to do it with formurltoattributes.

Perhaps this article may help

http://www.coldfusionjedi.com/index.cfm/2006/4/24/ColdFusion -and-Pagination

Posted: 16 December 2009 at 4:08pm | IP Logged

I finally figured out how to do this in last month (Nov. 2009).   I created client variables in script mentioned in my script (see my first posting).

See this file to see how I set up my client variables.
 2009-12-16_160645_pagination.txt