Jumat, 18 Desember 2015

Re: [MS_AccessPros] Import errors

 

No, the text is sometimes zero length strings. The text file being imported is using tildes as delimiters, and the fields in question have problems when there are two tildes in a row at the spot for the field in the input. So "~~" instead of "~12/25/16~".
Sigurd

On 12/17/2015 5:30 PM, 'Bill Mosca' wrmosca@comcast.net [MS_Access_Professionals] wrote:
 

Sigurd – What does the blank field look like? Open the text file in something like Notepad++ and switch on the option to show non-printing characters. Maybe the field is not really empty as in zero-length string.

 

Regards,
Bill Mosca,
Founder, MS_Access_Professionals
That'll do IT http://thatlldoit.com
MS Access MVP
http://mvp.microsoft.com/en-us/mvp/Bill%20Mosca-35852

My Nothing-to-do-with Access blog

http://wrmosca.wordpress.com

 

From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Monday, December 14, 2015 5:57 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Import errors

 

 

Is there a way to eliminate some of the errors that Access flags on
importing information from a text file?
In my case, there are some date fields which are blank in some records.
The import generates a new table, TextFileName-ImportErrors
For each row in which one of these date fields is blank this new table
gets a "Type Conversion Failure".

Should I import these fields as text and then convert to date fields in
another step after importing?

Thanks for any suggestions/help.
Sigurd Andersen


__._,_.___

Posted by: Sigurd Andersen <sigurd@solbakkn.com>
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (3)

.

__,_._,___

Tidak ada komentar:

Posting Komentar