You'll have to pass the list of Integers to the stored procedure as a
string, then handle them on that side.
The quick and dirty way would be to use dynamic sql to build and
execute your query as a big string, but then you'd have to spend the
rest of your career living in fear that some junior dev will dig up
your hacky code one day and call you on it.
What you'll probably end up doing is building a User Defined Function
in the database that takes your comma-separated list and hands it back
as single-column table that you can join into your query:
WHERE job_id in (select value from dbo.inline_list_split(@integerList)
)
Dig around in the SQL groups to find code to do the splitting for you.
Good luck!
Jason Kester
Expat Software Consulting Services
http://www.expatsoftware.com/
---
Get your own Travel Blog, with itinerary maps and photos!
http://www.blogabond.com/ jr********@gmail.com wrote:
I am using an objectdatasource with a .Net 2.0 ASP page.
The SQL for the tableadapter needs to use the IN operator as in
WHERE job_id in (111, 222, 333, 444, 555)
Job_id is a DBType Decimal and ProviderType Number
I have set the default value for the parameter to be
19620,19610,19580,19550 for testing
However, .Net strips the , and turns it into one large number.
How do I specify that it is rather an array or list of numbers,
esentially passing an array of numbers to the parameter?