Otis wrote:
Indeed they're missing, because where do they have to be set? The routine getas... query creates an IRetrievalQuery object and that's executed. It doesn't contain output parameters because there's no system to set them, as it would be illogical...
Which is why I recommended generating an additional method for each query in RetrievalProcedures which can be subsequently called to retreive the values...
The problem with doing this manually is that the index of the output parameters in the parameters collection in IRetrievalQuery may change when the code is regenerated.
If there was a generated method to pull the values from IRetrievalQuery's parameter collection code would not break when a re-generation occurs.
for each generated Get...AsQuery method you would have a corresponding
public void GetQuery...ReturnValues(IRetrievalQuery query, out int returnValue1, out int returnValue2, ...)
This method knows where the output paramters live (their index) within the parameters collections and can pass them out. See my example at the top of this thread.