Forum Discussion

CJW1960's avatar
CJW1960
Frequent Visitor
5 years ago
Solved

When importing Excel Workbook having Superscript text in Header it does not show the column involved

When trying to import an Excel Workbook,  using Get and Transform Data, having Superscript text in Header, it does not show the second column, having the Superscript text. However when double clicki...
  • PhilipTreacy's avatar
    PhilipTreacy
    5 years ago

    yeah understood CJW1960 , not surprising but worth asking.

    Is there no way to alter the way the XLS files are produced to stop the superscript characters being used?  Or to export the data in a different format like CSV?

    Phil

  • edhans's avatar
    edhans
    5 years ago

    Sorry CJW1960 - didn't see you had attached it already. Yes, like PhilipTreacy I get the error. There are twopossible ways to fix it.

    1. Remove the superscript char
    2. Convert the workbook to XLSX. I confirmed saving as XLSX fixes the issue.

    This is the second confirmed issue I've seen with XLS formatting and Microsoft will not fix. I reported this to them earlier this year and the product team looked at it and basically went "Yup. You are right, it fails, but we aren't going to spend any time coding around an Excel format that was EOL'd in 2007." And I fully understand.

     

    The only suggestion they offered was to install the Access 2010 Engine Redistributable. Links and more info here. That code actually has some stuff for XLS files. However, it did not fix my issue, so no promises here.

  • CJW1960's avatar
    CJW1960
    5 years ago

    Thanks edhans, tried the potential Access 2010 solution but as you said it did not fix the issue.
    Think i will create a workaround opening all files and saving before closing using a macro.
    Cheers, Kees

  • edhans's avatar
    edhans
    5 years ago

    Sounds good CJW1960 - I'm doing the same thing with a file I get 2x per month from an outside provider.

     

    Can you mark one/more of these posts as the solution so everyone will know the thread is solved and if they have the same/similar issue will know that saving the file as XLSX is the workaround.