MS Access设置忽略日期转换错误

Access DB导入固定宽度的文本文件;一列主要是日期。
当日期不可用时，文件的创建者实际使用字符串Null
Access将表中的行与该字段实际为空。

An Access DB imports a fixed width text file; one column is mostly dates. When the date is not available, the file's creator actually uses the string "Null" Access puts the row in the table with that field actually null.

但是，当文件开始使用不同的字段宽度时，我复制了DB，调整了输入规范中的起始/宽度值，并导入。现在，所有有空值的行都会记录（表）_import_errors作为将文本转换为日期的错误。

But, when the files started coming with different field widths, I copied the DB, tweaked the starting/width values in the input spec, and imported. NOW, all the rows with null get logging in (table)_import_errors as an error converting text to date.

我发现没有设置（不是我更改任何）到解释一下。一个区别是，尽管这两个数据库都是Access 2000格式，但原始文件仍然在一台仍然具有Access 2000的机器上，而新的数据库正在由Access 2003处理。

I have found no setting (not that I changed any) to explain it. One difference is that although both DBs are in Access 2000 format, the original is on a machine that still has Access 2000, while the new one is being handled by Access 2003.

Access版本中的行为是否改变？预处理文件是唯一的解决方案？

Is that a behavior change in the Access version? Is pre-processing the file the only solution?

谢谢David。这就是我所做的（除了Excel部分），如果它没有固定。我发布，但显然有人不喜欢公众承认Access有错误。

Thanks, David. That's what I would have done (except for the Excel part) if it had not fixed itself. I posted that, but apparently someone didn't like the public admission that Access has bugs.

唯一改变的是固定宽度纯文本输入中的两个其他列较宽。然而访问决定丢弃整行，而不是仅连续三次尝试的日期字段。第四次，它仍然将其报告为错误，但导入了该行的其余部分。

The only thing that changed was that two other columns in the fixed width plain text input was wider. Yet Access "decided" to discard the whole row instead of just the date field for three consecutive attempts. The fourth time, it still reported it as an error but imported the rest of the row.

所以，当Access不正当行为没有好的理由时，再试一次或两次，然后尝试从文本中明确地编码转换。

So, when Access misbehaves for no good reason, try again a time or two, then try explicitly coding the conversion from text.