Has anyone experienced this error when using an Excel spreadsheet as the source of a report? There are only 13 columns in the spreadhseet with only 1594 rows. When I experimented with the report, I found that when the 13th column was removed, the error no longer appeared. Is there a Excel column maximum for BO that anyone knows about? I looked up the error in the Users guide, Knowledge Base, as well as searched the Forum - nothing.
I did trick BO by saving the .xls as a .txt file and then import it in to BO and the error seemed to have disappeared. But, I would rather the user not go to that extreme at every import.
Any knowledge of this error would be appreciated - Thx!
We are on 5.1.3. We are using Excel 2000. And no, there is nothing special about the 13th column. Also, it does not matter what is in the additional column (numeric or text) from what I can tell…
Define your your 1594 rows as a Named Range and see if you still get the error. If not, then it is possible that you have multiple rows of NULL or blank data that BO is having issues with.
Great Advice! This seems to work for me, now I will get the user to try it. Also, great pdf’s out there on your link. I can especially use the cascading prompts example. Thanks again!!!
No problem, and thanks! Running some code to check the “used cells” will tell you exactly where the problem really is, but if this works, I’d go with it.
Well, I spoke too soon. The import worked for the user, but one of the columns in the spreadsheet disappears. The column is still there, but the data is missing. I have never seen this behavior before.
I recommended to her to make the Excel file a .txt and then bring it in to BO, but, she is not going for it - too much effort and she wants the product to behave as it was designed to (I don’t blame her).
Anyway, I almost ready to consult w/ Business Objects on the issue.
Your “column” of missing data wouldn’t happen to be a numeric column would it? If so… is there a character located in the column somewhere (or a blank cell really early in the rows for that column).
I’ve seen this when BO decides to treat a column as one datatype and then finds cells that contain another datatype.
What if you FORMAT a column to be the specific datatype before you attempt to import it? I’d have to see your actual data to be sure.
If the formula I sent will resolve the “missing” data, I’ll post that (or Robbie can post it). Otherwise, I’m still looking into the reason why it’s trying to import the entire document (and not just the used cells).
(BOB member since 2003-02-24)
(BOB member since 2002-06-20)
