Hi Mark,
IMO, I would suggest you create a single method which take the maximum
count of parameters and determine the select/filter code logic in this
method(or you can create several private/internal helper methods which do
select/filter according to the different paramter combinations). This is
because ObjectDataSource can only be configured to use a single Select
method at a time and it is not quite good to change it at runtime, so it's
better to only expose one public select method in our business logic class.
As Gregory mentioned, you can check the paramter value and do select
filtering in stored procedure(at database layer). Instead, you can also
move the parameter checking and select/filter logic in business class code.
It's up to you according to the detailed scenario.
If you have any further questions, please feel free to post here.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.