This really is a windows problem, but its Unix related. I am hoping to find a kindred spirit who can help me....
=> I know I can use a sed to add the ^M to the line end, but in my customer does not have a Unix environment. The supplying party is unwilling at the moment to help us. <=
In text files created by Unix a line ends (and in those cases the record) with a linefeed (chr(10)) If you then want to import the file into access it sees it as 1 long line.
Now i have found that to be a major pain, and one can work around by reading the file character by character. This however causes the import to take a very long time.
Also i have noticed that in a certain environment, using A2k sp-3 on a win 2k machine access will accept the chr(10) as the "carriage return" thus importing the file properly. On other systems tho, NT/A97 and XP/AXP, it sees it as one line.
Does anyone have any info on the how when and why of this? I tried googling, MSDN and searching on the forum, but could not find anything trully relevant. Except maybe that Access should see it as 1 line, except for the earliest version (2).
Anybody?
Thanx