> > record(s) but rather how many rows of the view were operated upon during

the

> > update (or delete for that matter). With insert it is always just one.
>
> What for insert...select.

Yes, of course. That's easy, how ever many records were selected. In the
case where you are doing an insert without a select it is just a singleton
insert.

I've not gotten to where I like to think of RowsAffected as RowsWalked. It's
really the only thing that makes sense to me and it is consistent whether
you are using a table or a view. And, when using tables directly,
RowsAffected is the RowsWalked. And when using views, it is impossible and
in my opinion senseless to try and report how its operations were physically
implemented. Whatever views do in triggers should be considered internal
protected details. What the client needs to know is simply, did you walk any
records and if so, how many.

FWIW,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com