nope >> UPDATE CASH_CHECK A is forbiden.. the alias must be set in the from clause.

It's like trying to tell whether it's better to be jewish or christian. Just go with what you believe is the best and experience will show you the rest...

Here's another one just for the fun of it :

Select SUBSTRING(@IDS, dtPositions.StartPos, dtPositions.Length) as IDS from

(

Select dtCommas.Commas + 1 as StartPos, MIN(dtCommas2.Commas) - (dtCommas.Commas + 1) as Length from...

HTH... This is just the start .

Glad to hear that...

I was trying not to piss him off (I know he's right)... but everytime I post that function (set version) I had to explain it in details and I got...

This seems to me that I would be simpler to have the application do the security work.

Maybe you could add a extra layer of security on the server where you'd...

This query cannot be used in an indexed view, so that solution is out.

Now why do you have 20 self joins on this query??

Can we see the table...

HTH.

That's not my strongest suit... I'll let the other dbas handle this one.

They are ok with losing a full days work of all database at the same time?????

Do they know that a 500 gig drive costs only a few 100 bucks... far...

HTH. Good luck with the rest of the work.

Why would you use something like this???

Why not make a proc to do the update.

One to do the select then just call 'em in the right order from the main...

Yup, that's a great workaround, but it doesn't solve the underlying problem of the bad perforaming view.

The indexed view would do just that, but as I said it doesn't solve...

What kind of power user will be using this??

Wouldn't it be simpler just to give them a crash course in sql?