Managing filtered recordsets with DA

I am trying to build using DA as a replacement for ADDT which I have generally used for my back-end for a number of reasons, not the least of which is the ability to manage based on recordsets as well as tables.

I am currently using session values and manually changing the SQL of the pages as necessary to accomplish this.

I know recordset management has been frequently requested. I am wondering if you have any tutorials or other documentation that might illuminate me on a better way to do this as I plunge forward. I would like to rely more on DA for my back-end, but so far, it is a lot more work for me.

What I want to do, for example, is to have a pages table with an idpage foreign key that refers back to the pages table. The pages are also tied to locations, so I need to filter for the current location (field = idloc). If idpage is 0, it is a top level page, otherwise it has the id of it's parent page.

The problem is persistence of the parameters of these filters. I can modify the SQL, but pass original query string does not seem to work and the hard links in the pages the wizard generates makes it a nightmare of a maze to ensure the parameters for idloc and idpage remain in the URL without duplicating as you navigate through the DA pages.

i too am trying to generate filtered recordsets and would love for a simple way or documentation without running through wizard completely to generate pages.

if you have any luck please let me know.

thanks

If I'm reading the question correctly, this sentence really is the key to your problems:

  The problem is persistence of the parameters of these filters. I can modify the SQL, but pass original query string does not seem to work  

the pass original querystring feature relies on the query string being present in the forms post.

In other words, if you have a page:
update.php


and you browse to it with a query string var:
update.php?id=4


and you have a form with the following action:
<form action="update.php" name="form1" method="post">
</form>

the query string is absent when the form posts, so the pass original query string setting does not have a query string to work with.


make sure any query string vars that are passed to the page are posted when the form posts, use the following for the forms action:

<?php echo $_SERVER["PHP_SELF"]; ?><?php echo (isset($_SERVER["QUERY_STRING"]) && $_SERVER["QUERY_STRING"] != "")?"?".$_SERVER["QUERY_STRING"]:""; ?>

example:

<form  action="<?php echo $_SERVER["PHP_SELF"]; ?><?php echo (isset($_SERVER["QUERY_STRING"]) && $_SERVER["QUERY_STRING"] != "")?"?".$_SERVER["QUERY_STRING"]:""; ?>" name="form1" method="post">
</form>

Hi Jason,

Thanks for responding. I understand what is required. The problem is, if I use the DA wizard to create the pages, and check the "pass original querystring" box, the DA generated pages do not contain links that preserve the query string.

If I enter the DA pages with idlocation=1&idstyle=3, the DA pages should preserve that query string in the links. In ADDT, I did have to add this kind of information to a just couple of links, but everything was on 2 pages (list and detail).

When I tried to do the same with DA, there were a lot more adjustments that seemed to be necessary. It just seemed to take too long and I wasn't sure I was covering all the bases. I'm losing the benefit of using the extension.

Currently, I am adjusting the SQL and using SESSION values to manage the persistence. I gather there is no better recommendation.

It would be great if the wizard could:

1. Generate it set based on a recordset as well as a table, and
   
2. preserve the querystring that exists when the user enters the DA pages throughout the links in the pages.

P.S. I know there are a number of ways to "enter the DA pages" so what I mean is that DA, I believe, only uses id=X, so it needs to add and drop that, but preserve the rest.

I will ad a feature request.

Thanks Jason.