Greetings Steveb!
Thanks - I am aware of this problem.
Basically, for some reason, on the first of the month, it has inverted the date format, and confused USA with UK dates. So 01/05/2000 (1st May) has become 05/012002 (5th January) - as usual - these things are not easy to fix!
I think the dates are correct in the database, so when the code is fixed, everything should sort itself out again.
With best regards,
Adrian.
Thanks Adrian, I thought that might have been the case.Iposted the post in case someone new( Myself being new)came across the site.
Halfway through typing the post I thought,"hang on,if I post it and youve fixed it", people would be looking at it thinking, whose the space cadet
so thanks for the quick reply
Regards Steve
Greetings Steveb!
quote:
Originally posted by steveb:
Thanks Adrian, I thought that might have been the case.Iposted the post in case someone new( Myself being new)came across the site.
Halfway through typing the post I thought,"hang on,if I post it and youve fixed it", people would be looking at it thinking, whose the space cadet
so thanks for the quick reply
Regards Steve
Never be afraid to report a bug. There are probably hundreds of thousands of lines of extremely complex code to a SQL Server database - there is always potential for things to go wrong - and then it is just a matter of finding what

Anyway - I think I have fixed it now - let me know if I haven't!
With best regards,
Adrian.
What's the time warp with the date,Jan wasn't a good mth for me, aaahhhh, Warp drive scotty, sector April
Should the date problem be fixed before a reply, "I'm not an idiot", it did say January, "didn't it".
Regards Steve
4 mths extra on ones life, hmmm, " LEAVE IT BE"