Trying to map all of my Select Stored Procs to the same Business Object is getting tough. I had hoped other developers would offer their methods to make sure the structure stays in sync.

Thanks for the reply. I think it's a good idea and was looking for somebody to either raise a red flag or say it was a good idea. Thanks!


>Hmmm, no replies yet. Well, here's my 2cents ... I have not used views in the past, but this sounds like a good idea to me. =0)
>
>~~Bonnie
>
>
>
>>I am having problems keeping my Stored Procedures in sync with my Business Objects. For example, I have a "Loan" business object that contains data from multiple tables joined in a Stored Proc. Now, when I have to create multiple Stored Procedures to return the same structure (Loan By ID, Loan By Last Name, All Loans) I have to replicate that same joining logic. Now, say in 6 months the user wants me to add another field to the Business Object - that means I have to update my business objects and find all of the matching Stored Procedures. What a pain.
>>
>>My new wild idea is to create views that map directly to my business objects. Every matching Stored Procedure would Select * from that view and then add it's individual criteria.
>>
>>Tell me if that's a good or bad idea. I know that Select * is generally frowned upon, but I think the advantages of doing it this way exceed that concern. Is there a better way to do this? Somebody stop the insanity!