sql datetime overflow error
Been programming a sql datbase routine, using c# and stored procedures.
Was working fine when tested earlier -- but now, when running online I am getting the error message as indicated.
Why would this be so?
Thank you in advance for your time and efforts with this enquiry.
Was working fine when tested earlier -- but now, when running online I am getting the error message as indicated.
Why would this be so?
Thank you in advance for your time and efforts with this enquiry.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
aneeshattingal: does this type of error happening when reading or writing data to db or both?
ASKER
I am catching this error via the exception error (and using a breakpoint) -- then hover over the ex value -- hence how I got to know this is a sqldate issue.
but...there is no reference (or easily visible) at which point this fails -- there are alot of date time entries within the database table and alot of differnet reading and writing going on.
so to get a feel where the error is actually occuring would be really useful as I only get this 1 error at the exception stage -- how can I search more intelligently for the error etc?
but...there is no reference (or easily visible) at which point this fails -- there are alot of date time entries within the database table and alot of differnet reading and writing going on.
so to get a feel where the error is actually occuring would be really useful as I only get this 1 error at the exception stage -- how can I search more intelligently for the error etc?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
JimBrandley: spot on !!! wow -- that is a really useful feature....
I cannot tell you how many hours I have poured over various scripting, adding logical breakpoints etc trying to capture various errors ... disabling certain lines of code, trying to isolate exactly where the issues are. very painstaking... wow, this hit the mark instantly -- I had 1 number incorrect so a db reference was pointing at the wrong location...a needle in a haystack normally.
thank you so much for this suggestion and advise...true gold nugget on this issue.
I cannot tell you how many hours I have poured over various scripting, adding logical breakpoints etc trying to capture various errors ... disabling certain lines of code, trying to isolate exactly where the issues are. very painstaking... wow, this hit the mark instantly -- I had 1 number incorrect so a db reference was pointing at the wrong location...a needle in a haystack normally.
thank you so much for this suggestion and advise...true gold nugget on this issue.
Glad that helped. MS has given us some great tools in this IDE. Unfortunately, sometimes they are not easy to discover. Good luck.
Jim
Jim
ASKER