Matthew,
Thanks for your post. We are still reviewing the best way to offer a solution for supporting stored procedures. A few things...
First... there is a major reason (which we discovered after release) as to why Dynamic Views cannot offer stored procedure support but rather basic SQL Query support. I will try and explain in a short summary and long, sorry if this gets boring.
Part of this has to do with the fact that we only select the top 'x' records and the fact that all of the search fields are filtered directly in the query itself and not at the code level. Our research has indicated that when the filter is added at the query level the performance is increased considerable. In order to do this was have to perform steps such as creating a temp table, only selecting the top records specified within the module config, etc...
Here are a few directions we can go with this.
1. If you are running SQL Server 2008 then we might be able to tell you a stored procedure you can modify within the application that should be able to offer more direct support. Right now the module only requires SQL Server 2005 and I believe SQL Server 2008 has the ability to more easily do a direct 'SELECT INTO TEMP TABLE' from a stored procedure.
2. We are working on another alternative for this but still reviewing based on item #3 below. The alternative is that we do an option in SQL Server called setting "SET FMTONLY ON" and then off. This gets us the column names and data types with no data, then we can build a unique temp table. The problem now is that since each module instance query or procedure is unique we don't know what columns are needed. If we do this more easily figure this out.
3. We are reviewing another alternative that is kind of holding back development on item #2. Basically this alternative is to filter both the count and the actual search filter at the code level. As I mentioned this isn't preferred because of performance however this also limits the module with other types of databases's. Right now if you have an 'External Connection' this won't work with Oracle because oracle doesn't process stored procedures and the 'TOP' x records the same etc... Oracle does not use Top X syntax. To do the same thing in Oracle, you have to: Select * from tablename where rownum < x etc... So, we might have to add an alternative option.
So... We are reviewing and working on the best way to handle this. If you need something handled outside of our standard patch or release schedule we can also handle this via our Premium Support services at
http://www.datasprings.com/Premium-Support. Thanks,
-Chad