Quantcast
Channel: Excel IT Pro Discussions forum
Viewing all articles
Browse latest Browse all 11829

Importing IBM 1140 files: worked in XL2007, not XL2010

$
0
0

Reposting to this forum at the suggestion of a support engineer (original post here)

Our company is in the middle of a mass migration from Office 2007 to 2010.

We have a report that is created from a mainframe; in Excel 2007 the team used Excel/Import/File Origin = 1140: IBM EBCDIC (US-Canada-Euro) as the source type. The report has not changed, but after the upgrade, this same File Origin does not recognize line wrap, and every piece of data in the file is added as a new column in Excel (all data is in Row 1). The test export file that was sent to me has a .export extension, and here is a partial sample of the contents:

ÁñññññÁñññññññññððÁñññññññññððÁñññññññññöòöñ÷òâ×@@@@@@@@@@â@@@@@@@@@@@ÅâùÂ@@@@@@öò÷ùõøÃÉ@@@@@@@@@@â@@@@@@@@@@@ÅÄÃò@@@@@@ó÷ùøøðÁä@@@@@@@@@@â@@@@@@@@@@@ÅâäÈ@@@@@@÷ðòôòóÃÂ@@@@@@@@@@â@@@@@@@@@@@Å×Ñé@@@@@@öö÷öõóÙÉ@@@@@@@@@@â@@@@@@@@@@@ÅÄÃò@@@@@@öôö÷õðÆÖ@@@@@@@@@@â@@@@@@@@@@@ÅÔÕÇ@@@@@@öñôô÷ø×ã@@@@@@@@@@â@@@@@@@@@@@ÅæöÃ@@@@@@òòù

I'm not familiar with how Excel converts from different formats, so the first question is whether there is an alternative source type we should be using instead, to get the desired results in Excel 2010. I went through and I think I tried all the built-in formats, with no luck. I don't know if there are additional source format converters that I can download.

In the meantime, I have written a small bit of  VBA to restructure the output (copy the data down to the appropriate rows), but that requires putting the VBA on the PC of every person who might need to fix one of these files, post-import. Finding a way to just import it correctly in the first place would be a much better solution. 

 

Thanks for any assistance.


Viewing all articles
Browse latest Browse all 11829

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>