Of course you can use a Stored Procedure!!! Isn't that the only way to access your databases??? <g> (Preferred way anyway, IMHO).

Anywho, you've almost got it right, but not quite. You need to also set the CommandType to be a Stored Proc. So, something like this:

oleDbAdapter = new OleDbDataAdapter();
oleDbAdapter .SelectCommand = new OleDbCommand("MyStoredProcedureName", oleDbConnection);
oleDbAdapter .SelectCommand.CommandType = CommandType.StoredProcedure;
oleDbAdapter .Fill(myDataset, "myTable");

Also, I wonder why you're using OleDbDataAdapter ... isn't this a SQL database? If so, you should be using SqlDataAdapter and SqlCommand. If not, just ignore me. <g>

~~Bonnie



>>>I had a thought when I woke up this morning. Can I pass a SP as an Adapter's SelectCommand?
>>>If it is possible are there any advantages/disadvantages for doing this?
>>>
>>>Einar
>>
>>I may not understand your question but here is something that I do.
>>
>>I have a Class that controls my data handling. When I use a DataAdapter I call a SP. Now as for advantages/disadvantages, I am guessing that allowing the SP to do “the work” would be better.
>
>I think you understand my question.
>This is in a nut-shell what I want to do:
>

>oleDbAdapter = new OleDbDataAdapter();
>oleDbAdapter.SelectCommand = new OleDbCommand("MyStoredProcedureName", oleDbConnection);
>oleDbAdapter.Fill(myDataset, "myTable");
>

>
>I realize how easy it would be for me to test this, but I just wanted to check here before I dove into that.
>
>Einar