Recent content by ionisz

Read my reply above about BOM characters now being inserted. Easiest thing to do (until MS fixes Access the way they have Excel) is to rewrite the file while stripping out the first 3 non-visible characters. To do that use Readline to read the string from the the file, and then for each...

An update as a FYI. It seems that the CSV specs have been extended to include a BOM or Byte Order Mark. This helps those with non English CSV files to import their files correctly. Unfortunately, the BOM requires that 3 hex characters be placed at the beginning of the file, to indicate if the...

Interesting. The first 3 characters in the field name list have ascii values 239, 187, 191 which are, of course, all non-readable ascii values. Looks like you were right, theDBguy! Strange that manual imports and linked files had no problems with this! I've opened a ticked with the author of...

Sorry about that - when I said freelance, it's more to keep me occupied. I'm a retired PM/Project Director who's enjoying retirement (5 years now) but every now and then like to program to keep my hands dirty.

Originally in the GTA, now in Tillsonburg

Good suggestion. I will test for that, but ... when I import manually it works fine, and if I link the table to the external CSV it works fine. So not hopeful, but good suggestion I will immediately test for.

I have been using DoCmd.TransferText successfully for years to import a CSV file into an existing table. The CSV file comes from an (external) application. In the past, the external app developer has occasionally changed the output fields, which has caused my app to bomb. No problem. I go...

My name is Ze'ev Ionis, I live in Ontario, Canada. I consider myself an expert in Access and VBA, having commercially built a number of applications. This of course does not mean that I don't have questions and can often get stumped on certain issues. Oh, and I'm always open to discussion...