Thanks for the reply as usual Sebastian. Is this by design - could it be modified in the future to support output params? I think it is the most efficient way of querying data and returning values (I use it on all paging stored procs). If so then I will raise an enhancment request.

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

Rodney,

if you need to get a single value out out your sProc only, ExecuteScalar should fit your needs; you simply need to RETURN the value instead of using an OUT parameter. From my experience, this is most usual use case.

I just reviewed interface of MS DAAB, and ExecuteNonQuery should return Out Parameter, but unfortunately the calling method in DotNetNuke DataProvider passes the parameter collection by value. You might enter the request for out param support into our issue tracker, however, this looks difficult to correct w/o causing a breaking change.

Rodney:

If you have gone the way of the DAL+ instead of the full DNN DAL, that means that you want to save some time, lines of code, and frustration, just like I do.  The DAL+ is fine, I was doing something like that even before DNN.  But, since ASP.Net 2.0 I started using the SqlDataSource Control and it works great.  You can use it against the default DNN database or a separate database.  In this way, you can also get support and samples from universal ASP.Net sources like this one and it works completely independent of the DNN implementation.

EDIT: Forgot to mention that I use the SqlDataSource strictly with Stored Procs with parameters, no dynamic SQL at all.  This is what I recommend you to do.

I hope I'm not flamed for heresy or blasphemy.

Carlos