Date Format difference between local development server and deployed server

Hi,
I have a current situation which is presenting a problem that I would like to overcome.
I am not sure whether this is something that can be managed from the visual studio environment or whether it is something that is managed from the MSSQL database side or whether it needs to be managed elsewhere.
Currently my developemt server expects interprets and processes date format data in relation to Australian conventions. When run on my local server it runs just fine. However when I put the exact code and pages up to the deployment server it runs an error.
It has been pointed out to me that the service where the website is deployed operates relative to Amercian based conventions and whenever the same pages are deployed to this other server environment it throws an error.

If I have visual Studio on my system running with ASP.net2 am I able to adjust some settings somewhere which would make the server perform relative to an American based system so that I can replicate the other system?

If so where and how do I make the changes.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Rakrus19y ago
In the code behind od your .Net Form set the dataformat of the datefiled you are using to a specific culture(i.e it is to australia or america).for this you can go through MSDN and seacrh for localization or globalization,otherwise search for cultureinfo class it will helps you.

If any Issues mail me at [email protected]