Yes, if I had more than one runner odds on, or so many runners that the probability was over 100% then the problem occurs.

However this is the standard Dutching formula...

LOL

I like it, that query is so SQL 2000, it was and did use old system tables but it still worked with a change to make nvarchar(max) appear rather than...

I know overlapping indexes are an issue but one a production system having a permanent DB which stores the missing index DMVs so you don't lose recommendations between server/service shut...

Hi, thanks for the replies.

I did try that 3 line SQL code, to set into Single User Mode and then change the DB collation before putting it back to multi...

Yes the ASP side is very tricky - not many ASP Classic coders left to ask!

Well done that fixed that results page but I don't understand why as I just checked all the tables in the SELECT statement and the ONLY one with a column...

I know they shouldn't that's why I am so confused to what is going on. I will try and insert some screen captures so you can see.

If you go here...

Yes as I said in the reply I only did the CONVERT on the SELECT column NOT the order by statement which is why I am so confused.

I had added...

I've been into IIS and changed the

.NETGlobalization - Culture and UI Culture to English (en). English (United Kingdom) en-gb

at both the server level and on the website levels as well.

That...

So your saying that all my SQL settings ARE correct then?

I don't suppose you know any GOOD (as in expert) forums that would deal with sort of issue.

I am guessing...

Come on this must be a standard issue many people have faced before - I am sure I used to come here years ago to find the answer.

Someone must have...

I just want to quickly add that putting

<%

'Set the server locale

Session.LCID = 2057

%>

At the top of the ASP pages does force the site to show the dates correctly as UK...

okay cool, Ill have to change my template for stored procs around then to use that format

Ok, I totally get that as I do use TRY CATCH and all the ERROR_MESSAGE() ERROR_LINE() ERROR_NUMBER() ERROR_PROCEDURE() functions to get detailed errors in TRY CATCH statements and log...

Regarding the GOTO statement, are people saying it has no place in TSQL either?

I know VB and remember on my Amstrad 64 having to use GOTO statements constantly so...