| T O P I C R E V I E W |
| AnonJr |
Posted - 13 August 2009 : 09:31:25
Its been one of those days... I may post about that later.
Remind me again why we are converting the date/time to a string and storing it as such...
I ask because I'm upgrading the online testing software where I work and in the process migrating to SQL Server 2005. I'm also tightening the integration with the forum, hence the question. As soon as I get the new structure planned out, I'm going to write the script to migrate the data from Access to SQL Server and if needed convert the date/time information. |
| 2 L A T E S T R E P L I E S (Newest First) |
| AnonJr |
Posted - 13 August 2009 : 11:12:11
That's what I thought. Just checking - that first cup of coffee didn't really help...
Since I want to make use of functions like chkDate, UpdateLastHereDate, etc. I'll probably use the same format. |
| HuwR |
Posted - 13 August 2009 : 10:04:04
it is because different databases and ASP all treat datetime variables differently, it is therfire much safer to store the data as either text (Snitz does this) or as an integer. |
