|About the delimiter, I can use any character that suits your needs. I put them in myself during the extraction. I tried using Æ, with same results, I suppose I'm limitted to something that falls within a certain range of ALT codes.|
It's a long shot but you could try adding a ^ before the delimiter in the script.
If there are no tabs in your text I would suggest it as a delimiter instead.
Extended ansi character like those you are using normally tend to work, but what I would consider "safe" characters would be 09h and 20h - 7Eh(an exception being the " character, it *should* work in these circumstances but a for /f loop won't split on it).
TEST RESULTS: Only the first FLIGHT record was not split, no more phantom ICAO record, everything else looks good at first glance.
I can't seem to replicate this either, I think I'm going to try re-writing the code later(I have to go to work now) as these inconsistencies call for it. Unfortunately even then I see no way to avoid adding the delimiter to through the script.....
Off-topic: Is there a freeware file comparison tool I can use to compare input and output text files?
We had utilities available for mainframe use, it would be nice to have something equivalent to check for changes, just to verify the changes I do at each step of file manipulation (there's many).
If all you need to do check the file is *somehow* different using xp's "fc" command could work, failing that perhaps a win32 port of the unix/linux "diff" may do the trick.
Batch Variable how to