Kevin,

Something else I'v been thinking about that I wanted to get your
thoughts on;

I am going to use Stored Procs to get data, and in mose cases, with a little
forethought, I can create SP's for most queries I will need.

But there is always the dynamic query to think about. I have a few apps
where the user decides the WHERE clause based in selections in a Query
screen.

Is there some way to handle this with Stored Procedures?

Thanks!



>Hey, Kevin,
>
>To answer your last question, assuming you're getting your result set back as a DataSet, you can do "MyDataSet.GetXml()" to convert the dataset to an XML representation.
>
>You're on the right track for your stored procedure example. Obviously, some tables might have multiple stored procs.
>
>Stored procs are generally the way to go. They allow you to develop and test result sets that are client-agnostic.
>
>Mine is set up to use a collection of parameters, since one stored proc might have one string parm, a second might have 3 parms of different data types, etc. You're going about it the right way, and you're establishing some good foundations. And even if you don't immediately intend to implement something (web services) for a distributed architecture, the better you structure things now, the easier it will be to fit them in down the road.
>
>Kevin