Another thing to be careful of with a CSV file is to make SURE that the 'embedded data string' does not itself contain any commas - this will throw off the input reader. For example, if you have a file and are describe it as Last Name-comma-First Name-Comma-Account Number and you have a piece of data that comes in like "Smith, Jr, John, 123455676", the reader will see the comma between SMITH and JR, setting JR in to the FIRST NAME buffer in the receiving file, and setting JOHN in to the account number field, which will, at best, cause a data mismatch error.
Embedded commas are fairly common in fields like LAST NAME or ADDRESS, if there is not a fairly strict data validation process in effect in the original data input process. After all, it's hard to make sure that something that's perfect valid like "22 East Maple, #44" doesn't sneak in, or the aforementioned "Smith, Jr" or "King, VIII, Henry" kind of stuff.
If your data stream MIGHT contain commas embedded in it, it might be better to set up a column-delimited input process, where you specify the start and end columns specifically for data, and embedded commas won't matter.
Just a W2TW...
Jim
Don't be sexist - Broads hate that.
Another free Access forum:
More Access help stuff at