Currently Being ModeratedNov 28, 2012 4:37 AM (in response to peteisams)
Have you examined an "xls file created by SRSS" to see if it is really an xls file? I have read (but not encountered myself) that some programs will create CSV files with the xls extension, which Excel will then quietly import. If that were the case with these files, changing the extension to CSV might allow Numbers to import them.
Currently Being ModeratedNov 28, 2012 5:10 AM (in response to Jeff Shenk)
I will take a look - I was going to test whether or not creating a CSV would work better anyway.
Currently Being ModeratedNov 28, 2012 5:25 AM (in response to peteisams)
Tested and definitely not coming out as an CSV - CSV works but without formatting, column names etc. I will try and investigate the file headers and see if I can work anything out. I think it might be something to do with the commication of the file - seemingly by forwarding it through outlook (as opposed to just emailing it from the report server) seems to add to it what ever it is it needs.
Currently Being ModeratedNov 28, 2012 8:34 AM (in response to peteisams)
I'm not sure what your last test was. You said it is definitely not a CSV but that CSV works but without formatting. Did you mean you changed the XLS extention to CSV and it did not work, you got gibberish, and in a separate test you created a CSV file (either by exporting it that way to start with or by saving it as a CSV in Excel) and the import worked but without some of the features/data you needed?
Also, you mentioned earlier that only newer versions of Numbers have this problem. Is it for sure that some non-updated versions of Numbers on the iPad will open these files? You've tested one of the recently created xls files to verify this?
Currently Being ModeratedNov 28, 2012 8:59 AM (in response to peteisams)
Was this the other post you mentioned?
It would appear that SSRS creates non-standard headers and Numbers doesn't know how to process them. I'm not sure what to recommend. CSV might work as a go-between except that it is only the data, no formatting. Is there any way to change the workflow on your end so that the generated file goes to someone at your company who then re-saves it in Excel and emails it to the client(s)?
Alternately, if the client only needs to read the data, not interact with it and make changes, maybe another app will read the files correctly. You could give GoodReader a try.
And another alternative might be for them to use Quicklook instead of opening the file in Numbers. Not another app, it is one of the options for opening the document on the iPad. I don't know if Excel readbility is a built-in feature of iOS or if I can read Excel files because of some app on my iPad. Something you can test I hope.
Currently Being ModeratedNov 28, 2012 1:50 PM (in response to Badunit)
Hi - thank you for your responses. I don't have an iPad so testing is all being done on site.
The report is based on three tabs, each producing a basic table with data in. I can create the reports in CSV and they work fine although the format is all wrong (no tabs etc etc) - but that would lead me to believe that it is nothing in the actual data which is causing the load error. It also seems fairly intermittent, so I tested with a few different file sizes to make sure it wasn't this - and again nothing too conclusive there.
I presume quicklook is the built in function to view a file, I spotted this today but again it won't open in that or then again when asked to open in Numbers.
Hunting around this forum it seems there is some issue in general with opening some XLS files (especially ones created by SSRS) depending on iOS version, so that is the route I will be looking at tomorrow. Putting these files through a save loop in excel isn't really an option, so I am going to test with a go between e-mail tomorrow which has in some cases seemed to do the trick - maybe appending something to the original file. Some other posts have suggested that an XLSX file seems to work a lot better and that is supported in MS SQL 2012 which is on the way for our customers at some point.
Definitely an awkward one!