|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary
[1,407]
Women 4 times more likely than men to cough up personal info
[589]
Japan's 10 funniest tech-related commercials [Videos]
[407]
Throwing away a promo CD is "unauthorized distribution"?
[1,265]
Adults too quick to dismiss educational video games
[682]
Attack of the iPhone clones [Slideshow]
[578]
10 things IT needs to know about AJAX
[1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow]
[409]
|
|
xml to usable stuff
If the XML file is text - which it should be from what I've seen - you can use PERL or code that works like PERL to search for key characters and sequences of characters. If you really need Excel as a final product, you should be able to build a resulting .CSV like file that Excel will import with no problem. If you want to do it in one step, macro running from a button calling code to open the file should be easy enough.
MS supposedly makes it "easy" to pull apart XML files in .NET. However, if you aren't trying to parse the entire file but find specific pieces, I thought their approach was overkill when they tried to teach it to me a few years ago. I could write a piece of code in QBASIC to pull out a few specific fields faster than I could write code "their way." Admittedly, their code may be easier to change than mine, but it will depend on how often you think the input file will change as to your approach. To a fairly novice coder, it might be easier to do it the MS way for a permanent solution; but I was pulling fields out of 255 character report rows wrapped at 80 characters 10 years ago, so maybe I've got an advantage.