That's why I used 1/1/1900

IWETHEY v. 0.3.0 | TODO

1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User

Welcome to IWETHEY!

Post #403,991

by lincoln

8/12/15 1:28:48 PM

That's why I used 1/1/1900

because I was getting numbers like "42221.00" in Excel. Subtracting that many days from today put it around the 3rd or 4th of January, 1900. Knocking off the 2 additional days made all of the dates in the spreadsheet match the dates in the SQL table.

Satan (impatiently) to Newcomer: The trouble with you Chicago people is, that you think you are the best people down here; whereas you are merely the most numerous.
- - - Mark Twain, "Pudd'nhead Wilson's New Calendar" 1897

Trying to format a Excel column as Date from VB.Net - (lincoln) - (10) - Aug. 7, 2015, 10:38:29 AM EDT

Does the case matter? - (Another Scott) - (1) - Aug. 7, 2015, 11:56:05 AM EDT

just for grins - (lincoln) - Aug. 7, 2015, 01:23:04 PM EDT

This worked, but it takes longer - (lincoln) - Aug. 7, 2015, 04:38:37 PM EDT

How do you export/import? - (scoenye) - (1) - Aug. 7, 2015, 10:02:14 PM EDT

The batch process has a program that uses a SQL Bulk Insert - (lincoln) - Aug. 8, 2015, 10:47:55 PM EDT

Well, they won't let me use a varchar - (lincoln) - (4) - Aug. 11, 2015, 01:26:11 PM EDT

The only way I can reproduce is if the cell contains a string - (scoenye) - (3) - Aug. 11, 2015, 04:05:01 PM EDT

StartDate = "01/01/1900" -NT - (lincoln) - (2) - Aug. 11, 2015, 08:15:33 PM EDT

The epoch start date is 1900-jan-00 - (scoenye) - (1) - Aug. 11, 2015, 10:35:00 PM EDT

That's why I used 1/1/1900 - (lincoln) - Aug. 12, 2015, 01:28:48 PM EDT

iwethey.org

We are trying to save children from evil forces. This wisdom tooth is not a good sign.
40 ms