>I asked kind of the same question on SQL Server forum, specifically using VFP as the language of choice. But I was wondering also how .NET developers address this design. How do you do the following update of SQL Server tables?
>
>Say you have 3 or 4 tables that a process need to update. For some tables only one record is to be updated. For others, several records. For some tables, the records/rows that are to be updates are not known until records of another table are processed. So it is kind of sort of a complicated business logic. But at the end, some tables and rows have to be updated.
>
>Do you use Stored Procedures for that? If you would not want to use Stored Procedures (which is what I would prefer), how do you conceptually address this problem?
>
>Thank you in advance for sharing.
I do these kinds of updates in a DataSet. 7 Tiers is the way to roll nowadays!
DATA
[Tables/Views -> Stored Procedures] ->
BUSINESS
[DataSet -> Business Logic] ->
[Business Objects] ->
INTERFACE
[Web Service -> Interface].
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only