This is just an FYI to help anybody that might be in a similar situation. I did not have to write or execute any UNIX script to remove these troublesome CR/LF hex characters from the text in several fields in one of my MS Access tables.
First of all, the MS Access Table in question is actually linked via an ODBC connection to an MS SQL Server database.
After establishing the link and being able to view the data, I export the data using the tilde (~) as the delimiter and using the quote (") to surround text fields .... and save the file as a type .txt or.csv file. I made sure that the tilde did not exist in the Table prior to selecting it as my delimiter.
Once the export file was created, I used an awesome tool which I found and downloaded from the internet to edit out the CR/LF characters.
The hex editor tool used is called XVI32. Link provided here:
http://www.chmaas.handshake.de/delph...vi32/xvi32.htm
Since MS Access also puts out CR/LF characters as it exports the data, I had to find some unique sequence of characters either from the end of the record ... or the beginning of the record that is on either side of the hex 0D 0A that MS Access puts at the end of each exported record. I then performed a hex replace of the sequence of characters with some other unique sequence of characters.
For example: the sequence of characters I found to be unique were: 73 65 71 75 65 6E 63 65 0D 0A
The 0D 0A shown here was actually put there by Access.
The tool allowed me to change this sequence to: 73 65 71 75 65 6E 63 65 7C 7C
I replaced the 0D 0A with a 7C 7C.
The hex 7C character (shift-\) did not previously exist in the Table either.
After that completed, I am then able to delete (or replace) any other occurrence of 0D or 0A that exist in the file .... i.e. the occurrences that I want to remove/replace that exist in the free text fields of the record.
Now, once that completed, I then change back the sequence of characters from 73 65 71 75 65 6E 63 65 7C 7C to 73 65 71 75 65 6E 63 65 0D 0A.
I then save the file (with a new name ... just 2B safe). I now have a .txt file that MS Access will be able to re-import correctly ... or just link to ... as desired.