"Doug Kanter" wrote in message
...

"David Biddulph" wrote in message
...
"Doug Kanter" wrote in message
...

"David Biddulph" wrote in message
...
"naulerich" wrote in message
...
I did remove the double quotes and added a ~ instead of the commas, I
am
still not getting the output in the correct columns when using the
import
with delimiter set to ~....I don't know what to do next...

You shouldn't have removed the double quotes, and you didn't need to
change the commas to tildes. Go back to your original file.

You should use your comma as the delimiter, but in the "text qualifier"
box of the text import wizard you need the double quote symbol.

Unless I misread the original post, he said there were commas WITHIN the
text that he wanted to keep intact - not just commas as delimiters. If
this is the case, Excel will split fields based not only on the commas
which exist as delimiters, but also when it sees those within the text.

No. That's what the text qualifier sorts out for you. Try it.
--
David Biddulph

In theory, yes, but the OP e-mailed me some of her original text (with
commas, not tildes), and doing what you suggest, the import does NOT work
correctly. Excel sees the commas WITHIN the text strings as delimiters,
same as the ones BETWEEN the text strings. Here's the text she sent:

"5493", "BASE-(Claims) Auto Format Update I", "Today most of our sites are
utilizing the WEBMD_NSF Format. To ensure that all sites are prepared for
MSP, electronic secondary, and using the latest claims submission formats
we must prep for migrating sites to the latest 4E format. This requirement
is in sync with the EDI requirement with the same name. This is a
multi-step project.", "Today most of our sites are utilizing the WEBMD_NSF
Format. To ensure that all sites are prepared for MSP, electronic
secondary, and using the latest claims submission formats we must prep for
migrating sites to the latest 4E format. This requirement is in sync with
the EDI requirement with the same name. This is a multi-step project.",
"<<internal source group", "Have to Have", "", ""

"5501", "BASE_Patient/Account Alert in Check-in", "Patient Alerts do not
currently work in Patient Check-in. So unless the front desk brings up the
detail on the patient, alerts are not presented to the user causing them
to miss critical items at the first contact with the patient.

By presenting this alert when the patient is chosen on the check in list,
the user will make or take the proper action necessary based on the alert
message.", "Need to activate Patient and Account Alert during patient
check-in.
Not currently working in Patient Check-in.", "<<internal source group",
"Nice to Have", "", ""

"3943", "BASE-Account Select Window Default Method", "Intergy today allows
users to designate their user preference when selecting patients. Users
would like to have this same feature when selecting accounts. By providing
the user to designate their "default" account select method in user
preference, it will allow them to save key strokes in the account select
windows.", "Provide the same method in Patient Select Window -- ability
for the user to default their search.
In the User Preference for Patient Select we called the Preference --
"Select Patient Sort/Filter Default". Need to do the same for Account
Select.", "<<internal source group", "Nice to Have", "", ""

If you change each occurrence of , " [comma, space, double quote] to ,"
[comma, double quote], then it will allow the import wizard to pick up the
double quote text qualifier art the start of each field, and hence it won't
split the field at a comma within the double quotes.

The only remaining problem is the additional double quotes around "default"
in the final data set. As Dave Peterson has said, in that case you'll need
to double up the double quotes. It then works OK.
--