I agree with AndyG. Most of the recordsets that I use are more involved than what is currently supported. I need to be able to pull data from several tables and have multiple parameters. If the grid could pull from a Recordset that is already done, it would solve the problem.
Michelle Glad I am not the only one needing this. As much as I'd liked to use this extension I am somewhat disappointed in its lack of functionality to access a pre-defined Recordset! I bought this and paid good money for it and have been totally unable to use this because of this simple lack of usibility. As it stands I am totally unable to recommend this extension until such time as this feature is implemented. Hopefully you guys will make this a priority and enable this soon. regards AndyG.
1. The Ajax Datagrid - fetches its data trought Ajax - so it calls a different page and not the current one (where you might have your recordsets)
2. The Ajax Datagrid constructs its own recordset on the fly! This is because those recordsets needs to be specifically filtered, paged and sorted depending on the grid selection on the page. This is just not supported by Dreamweavers own recordsets.
3. You can do complicated queries with Ajax Datagrid - it is not a problem! Just save them as a View in MS SQL/MySQL or as Query in MS Access. Then you can just choose them from the tables drop down.
I hope it is a bit more clear not - let me know if you have more questions.
I agree with the above postings..... using existing DW recordsets from the server behaviors tab would be nice, but I understand there are issues with this playing well with Ajax.
So could we have all of the filter options a DW recordset offers available in the DataGrid recordset: variables from cookies, form variables, and more complex filtering? One example of more complex filtering I could use now is based on if a date has pasted, like this: SELECT * FROM eventcal WHERE enddate > NOW() ORDER BY eventcal.startdate
Please keep in mind that some of us out here only know enough about hard coding to be dangerous. So built in filter functions are better.....
Regardless, I still think this extension is great! Thanks.