Hi there. I was wondering if it is possible to use SQL against a ProDataSet?
No. That won't work. What are you trying to do that an open query can't do?
Hi Mike. Our .NET client-side developers would like to filter the dataset they receive. Currently I provide separate input value parameters in Get procedures I provide (using ProxyGen). Then I use QUERY-PREPARE against the input and output dataset.
Any suggestions for receiving and using atleast the WHERE portion in SQL and using it.
Ah! You should have mentioned that it's a .NET client in the first post...
Will DataViews work for you?
http://msdn.microsoft.com/en-us/library/system.data.dataview.aspx
They provide a filtering and sorting mechanism for DataTables.
I am not sure that is what I was looking for. It would be on the back-end Progress side that I was thinking of using the SQL received from the client-end. I could send the full table to the client and then they filter on that perhaps but that seems inefficient.
The main question I guess is how can the client provide a filter (assuming they know the table fields) to the back-end to use on a ProDataSet and return the dataset?
Why is this anything other than simply providing some appropriate parameters which the server code can use in filling the dataset? The client shouldn't know anything about the implementation on the server so it would be quite inappropirate for it to be supplying actual SQL code.
Yes I agree with you. And that is what I am doing right now, just providing parameters.
Good man! Right thing to do. Encapsulation, encapsulation, encapsulation.
Finito