Hello,
I have a web ASP.NET 2.0 question. I am executing a local procedure through the API and sending over some membership dates as datetime.
For example, my stored procedure will send over expr_dt as '2009-06-30 00:00:00.000'
The problem I am having is on the ASP.NET side. I am retrieveing the data as
'2009-06-29 10:00:00'
Wierd!
Something is happening in the translation. I was hoping someone might know how to combat this.
For the moment, I just converted the datetime in my stored procedure to varchar expression 101 and then in ASP.NET 2.0 convert it back to datetime.
I looked at the standard API calls that send over date and they appear to be datetimes and I receive those fine, so I am not sure why my local procedure has the issue.
Thanks for any help,
Christian @ The Tech
This is just a guess, but could it be something to do with the timezones of the servers? The reason I suspect that is that it's 2 hours off....
I think you can hard code the value in these steps, then you can see which step goes wrong.