Is there an error message or a trigger on that table??

Yup 0 = 1900/01/01 so it's definitly a date .

Which part is giving you difficulties?

Forgot that one... can't use set options in functions... any way you can make this a proc?

1 row won't take "much" longer. Try fetching 1k rows in a join or a range search then rerun after the reindex, then you should be better off.

Ya, just make 2 different functions. One with the order by desc and <= @Date and the other one like I did. Cal the one depending on the...

So did you try my query before telling me it's not working???

SELECT tblOne.NamesOne, tblTwo.NamesTwo

FROM tblOne, tblTwo

where tbltwo.NamesTwo LIKE tblOne.NamesOne + '%'

This is assuming that you want the 1st name to be in the first part of the 2nd name.

HTH. Don't forget that it's also faster to call RPC than sql batch (for a single operation).

That's the way... and then restart the server to get the new name in action.

So it's just locked... waiting for the loop to stop sending requests (the loop is part of the statement to execute so it acts as a single operation, not like...

No that's fine... the points get across better that way .

What happens if you stop the first loop after you started the second window's update?

Think about it, you're concatenating text >>

me.txtbox = '5; DROP TABLE X--'

MyVar = "Exec dbo.MySP " & me.txtbox

And boom, you're screwed (maybe that one doesn't work but I've seen it...

The point you're missing is that I have a code generator .

Anyways your version uses dynamic sql which is subject to injection attacks. ...