The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
Please vote in the Forum Structure Poll. Polling will close at 2PM EST on January 21, 2025.
MS ACCESS import help
Deebaseron my way to work in a suit and a tieAhhhh...come on fucking guyRegistered Userregular
Someone on my team has imported a file. This file has some rows with null values, particularly in the first row. When they import and set the field type as datetime, if there is a null, access converts the entire column to GENERAL (ie 2/15/2012 becomes 49054).
This is annoying.
Short of ensuring the columns in the first entry are not null (impossible), is there a workaround to force a column to be datetime?
Posts
Access is saying "fuck you" in response.
Worst case, datetime as a number is still usable, she'd just have to convert to date first in any calculations?