Re: Nested Updates using SQLCLIENT classes
- From: "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx>
- Date: Sun, 23 Mar 2008 08:34:24 -0400
BK wrote:
Thanks guys for your insights. The problem is not suited to a
set-based solution, Hence the problems. I will look at poting it as
Bob suggested. many thanks.
Even if the problem is ill-suited for a set-based (or series of set-based)
solution, I would not suck all the data into a client structure to perform
operations that could be performed in a stored procedure.
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"
.
- References:
- Re: Nested Updates using SQLCLIENT classes
- From: Bob Barrows [MVP]
- Re: Nested Updates using SQLCLIENT classes
- From: Ralph
- Re: Nested Updates using SQLCLIENT classes
- From: Bob Barrows [MVP]
- Re: Nested Updates using SQLCLIENT classes
- From: Ralph
- Re: Nested Updates using SQLCLIENT classes
- From: BK
- Re: Nested Updates using SQLCLIENT classes
- Prev by Date: Re: Nested Updates using SQLCLIENT classes
- Next by Date: Re: Getting a List of Databases in an SQL Server Instance
- Previous by thread: Re: Nested Updates using SQLCLIENT classes
- Next by thread: Re: New to Access
- Index(es):