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.