In my program logic I need to delete datarows from time to time but not to
actually update that data to the database(its only needed for the algorithm
calculations). On the other hand, in the same algorithm, I do need to insert
a real record.
I wonder if simply eliminate the assignment of UpadetCommand would be
enough, or is there any other way to do it?
Regards

Based on what you have stated, I would consider a different method of using
this value than storing it, as it sounds like it is just an intermediate
value.

I see nothing wrong with updating the same temp value over and over again as
long as you will not need multiple threads updating that value. This leads
to two possibilities, neither of which is pretty.

1. Value locked when you try to write and causing failure for that user

2. Value overwritten before user 1 is finished with it, giving him/her a
wrong calculation.

If I were you, I would consider moving a bit out of the drag and drop world
and creating either stored procs or functions that do the intermediate steps
rather than attempt to use the automagic update bits on your temporary
values.

If I am off base and misunderstand what you are saying, either ignore this
or post a clarification.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

Subscribe to my blog
http://feeds.feedburner.com/GregoryBeamer#

or just read it:
http://feeds.feedburner.com/GregoryBeamer

********************************************
| Think outside the box! |
********************************************
"Ronny" <(E-Mail Removed)> wrote in message
news:Or$(E-Mail Removed)...
> In my program logic I need to delete datarows from time to time but not to
> actually update that data to the database(its only needed for the
> algorithm calculations). On the other hand, in the same algorithm, I do
> need to insert a real record.
> I wonder if simply eliminate the assignment of UpadetCommand would be
> enough, or is there any other way to do it?
> Regards
>