Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Excel / New Users / March 2008

Tip: Looking for answers? Try searching our database.

CDHS Object Codes in XL not clean

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
davegb - 21 Mar 2008 21:08 GMT
I imported a list of codes from Word into XL. I then parsed out the
parts I needed to create a table of those codes and their descriptions
to make them easier to use. A couple of MID commands did that fine.

Now, I'm trying to do a vertical lookup, using the code as the
reference to retrieve the description. When I copy the code from the
list and put it in the reference cell, the VLOOKUP works fine. When I
type in the same number, I get a #NA error. This tells me there's some
garbage in there with the codes that is preventing VLOOKUP to
recognize it. I've deleted out extraneous spaces, so that's not the
problem. Any ideas as to what's come in with the data from Word that
would cause this, and how to fix it?

Thanks in advance.
Jim Cone - 22 Mar 2008 02:29 GMT
Try running the "Clean" function on the data.
Signature

Jim Cone
San Francisco, USA
http://www.realezsites.com/bus/primitivesoftware
(Excel Add-ins / Excel Programming)

"davegb"  
wrote in message
I imported a list of codes from Word into XL. I then parsed out the
parts I needed to create a table of those codes and their descriptions
to make them easier to use. A couple of MID commands did that fine.

Now, I'm trying to do a vertical lookup, using the code as the
reference to retrieve the description. When I copy the code from the
list and put it in the reference cell, the VLOOKUP works fine. When I
type in the same number, I get a #NA error. This tells me there's some
garbage in there with the codes that is preventing VLOOKUP to
recognize it. I've deleted out extraneous spaces, so that's not the
problem. Any ideas as to what's come in with the data from Word that
would cause this, and how to fix it?

Thanks in advance.

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.