Hi guys,

I've had to drop it to pick up something else but not before changing it to Jeff's intermediate solution with regards the WHILE loop. This made a difference....

Thank you very much Lowell. Just had a quick scan and although this is new to me I'm thinking it might be a possibility. About to sign off...

I can't say for sure but I'm fairly certain that even if it's in-house then getting it fixed at source won't be an option. :angry:

There is the possibility that...

The user data is input using a different application over which I have no jurisdiction. This is the reason we have gone this way. I could do inline...

Yes, thank you very much. That is exactly the route we have gone down by wrapping a function round each such field that converts. This was going to...

This is a cut down version of the code....

The parameters include the dynamically built WHERE clause and a few of the switches to determine whether to return a table or...

Well it's not that there are different COLLATEs for different columns; it's more that when the users run a SP there may be case sensitive fields that they are searching...

Bleurgh!!!!

Ok, thanks very much for your help.

Might try to add a COLLATE for each relevant column where we build our WHERE string.

Could be messy. :pinch:

Hi,

Thanks for that. I should have said that I had decide to use that Collation. My problem is whether or not it will fit into my SP...