Numbers to Excel (2003 or 2007)

I heard many state you can't save Numbers in xls or xlsx formats. Is there an alternative way or than mailing it to my house computer and then saving it into either format? 99% of my work is xls xlsx edition.

i havent bought Pages, you mean from Numbers i will copy the sheet that i want to copy, then open the Pages Apps, then paste the data to Pages, then save it as Doc, then walaaa i can open it in Doc format in and paste it again it excel, not a solution but i think if my undestanding is correct, this may also help. Please confirm if my understanding is correct?

Similar Messages

Upgarde Excel 2003 to 2007

Hi ,
We are dev stage and we are using MS 7.0 version with excel 2003 .
we are planning to move excel 2003 to 2007 in comming days .
Pls let me know what are impacts , if we upgared excel 2003 to 2007 for BPC developument .
Regards,
PSR

Hi,
Migrating from Excel 2003 and Excel 2007 should be smooth if you take care of the reports, Input Schedules and Dimension Membersheets. Please make sure that all the reports and Input Schedules are properly resaved with correct extension like "xslx" for 2007. Also make sure you have compatibility pack installed on the users machines.
If all of your users are being migrated at once , this would be good, in this way you can avoid the few users opening in Excel 2003 and few opening and saving in Excel 2007. Also if you are migrating in phases, then make sure that BPC Admin users who access the dimension membersheets use one version at once. Because if one Admin User makes changes to dimension sheet in 2003 and the other Admin user open the same membersheet in 2007 then you might get issues like "invalid index format" error and your dimensionsheets might get corrupted. So make sure that all Admin users use same Excel Version. If these things are taken care then migration should go smooth.
Thanks.

OBIEE 11.1.1.7 Exporting to Excel 2003 and 2007 difference

Hi
I have a simple analysis, a couple of measures, some formatted so tat if they are negative show them as Red, minus, 1 decimal and thousand separator. Another measure is not formatted to be Red, just black, minus, 1 decimal and thousand separator.
So ... now to the issue. When I export to Excel 2003 the measures are fine, the numbers are numbers, all fine and dandy.
When I export to Excel 2007+ ... the red minus numbers are now text and impossible to change them all to number. I can only convert to number those that are less than 1000 ... the rest are just impossible.
The other measures, the ones that are black, minus, 1 decimal and thousand separator ... are numbers in Excel 2007+.
Why?
What can I do to solve this?
Kind Regards

Sorry guys ... forgott to say that I'm not the one exporting to Excel ... is my business user and I cannot ask them to save the reports to another format or to cast a column or more?
I will try them both and see what happens ... but this is something that Oracle must fix. It's the year 2013 for godness sake!! This is not a Beta software. In my opinion this is so ridiculous I can hardly find words for it hahahaha
I have tried to cast and convert ... well that doesn't work and I found that some people are using macros to convert text to numbers in Excel ...
Sub txttonum()
For Each tcell In Selection.Cells
If TypeName(tcell.Value) = "String" Then
tcell.Value = Val(tcell.Value)
End If
Next
End Sub
As goes for the CSV option ... I just cannot ask my business user to copy from a CSV file to the Excel file they want to work on, not even if they are advanced Excel users.
Thanks for your suggestions, I really that the cast would work ...
Any other suggestion.

Start OutlookSoft 4.2 with Excel 2003 when Excel 2007 is also installed.

Does anyone know how to get OutlookSoft 4.2 to use Excel 2003 as the default u2013 when both Excel 2003 and 2007 are installed? Iu2019ll take any suggestions. Thanks.

Thanks, Joost and Sorin, for your responses! We will be considering both of them.
My name is Christine, and I work with Ellie (who originated the question).
Sorin, where do you insert the launch command described in your response?
Neither Ellie nor I are computer programmers. We have learned on the job as we go. So it's not obvious to us what to do with your command/path. I have changed the "Open With" property for Web Excel to use the exe file for Excel 2003, but the result is that Excel 2007 opens in compatibility mode, and not as Excel 2003.

Excel 2003 reports

Hi,
I’m working on a system (set of PL/SQL packages) that builds Excel reports.
Structure of reports is (to some extent) defined by a template (also an Excel spreadsheet).
If you are interested in this functionality, you can visit:
http://apex.oracle.com/pls/otn/f?p=30285:16
Unfortunately currently it works only with Excel 2003 and (I hope) Excel 2007.
If needed it could be changed to work with older versions.
Lev

Hi, Denes
Yes, I'm using xml. When template is uploaded it is
analyzed and is broken into parts more or less close to its schema. I found description of the schema on MS website but some information had to be "reverse engineered".
When the report is built it is built from these parts. There is no expensive XML analysis at this stage (templates are very big, sometimes). Unfortunately not all functionality of Excel is allowed in Excel 2003 (pictures and charts, for instance not allowed). But as far as I understand in 2007 everything will be available.
Currently only Excel 2003 and 2007 could view the results.
I saw your very good package that returns Excel spreadsheet as an html page. I think it could be used – create report template as an XML (because it easy to analyze) but present it as html that could be viewed by all versions of Excel starting from Excel-97.
Thanks,
Lev
Message was edited by:
le

Report Manager - Template Conversion Problems Excel 2003/2007

Hello,
We are having an issue in which templates created using excel 2003 are showing incorrectly formatted outputs in excel 2007. We have performed testing by creating new templates in Excel 2007 and most formatting is correct as long as we only make minimal changes to the initial template. Once the template is changed to a further extent the formatting is correct but no actual output shows, just the token defaults. Patches have been applied for both the issue of incorrect formatting caused by Excel's smartcutandpaste and also the problem with the token defaults showing instead of actual Oracle data. We would prefer not to have to recreate the templates as this would be a lengthy process. To me it seems as something was modified that affected the existing templates (other than the Generic FSG Template, which works fine), but does not affect newly created templates. Other methods of viewing the data work fine (pdf and html).
Any ideas?
References:
Patches Applied to try and fix problem: 8792030, 9020608, 86607013
Metalink Ref: 960409.1, 1082349.1, 811853.1
Thanks,
-Steve
Edited by: sanstey on Oct 15, 2010 12:08 PM

The BNE.log for the report that would not show the data (due to column deletion):
10/20/10 3:12 PM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
10/20/10 3:12 PM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
10/20/10 3:12 PM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
10/20/10 3:12 PM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
10/20/10 3:12 PM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
10/20/10 3:12 PM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
The same error appears on the report that works fine (one without deleting columns):
10/20/10 3:22 PM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
10/20/10 3:22 PM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
10/20/10 3:22 PM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
10/20/10 3:22 PM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
10/20/10 3:22 PM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
10/20/10 3:22 PM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
The client is testing now and believes the report output is what she needs and will not need to delete the columns afterall, but for my curiosty, any ideas?
Thanks,
-Steve

Best practice for Smartview when upgrading from Excel 2003 to Excel 2007?

Does anyone know the best pratice for Smartview when upgrading from Excel 2003 to Excel 2007?
Current users have Microsoft Excel 2003 with Smartview 9.3.1.2.1.003.
Computers are being upgraded to Microsoft Excel 2007.
What is the best pratice for Smartview in this situation?
1. Do nothing with Smartview and just install Excel 2007.
2. Install Excel 2007 and then uninstall and reinstall Smartview
3. Uninstall Smartview, Install Excel 2007, and then install Smartview
4. Somthing else??
Thanks!

We went with option 1 and it worked out fine. Be aware that SV processes noticeably slower in Excel 2007 than 2003. Many users were/are unhappy with the switch. We haven't tested SV v11 yet, so I'm not sure if it has improved performance with Excel 2007 or not (hopefully it does).

EVDRE - Excel 2003 vs Excel 2007 performance

We run BPC 7.0 sp6 with a user population that has a mix of Office 2003 & Office 2007 on their client machines. We have several standard and non-standard evdre reports. Reports that are run in 2003 take 30 - 60 seconds to expand or refresh, the same reports run in 2007 take 3 - 10 minutes to expand or refresh.
Also, reports that are run consecutively only with different criteria in 2003 run fine, in 2007 each consecutive run adds 2 - 5 minutes per.
Does anyone know why?
Does anyone know how to fix office 2007 performance issues?
Any help would be appreciated

Hi Steven,
Have you installed System Driver Data Connectivity components on your application server (which is a prerequisite for running Excel 2007)? If not, then get it installed. This you can get from the Microsoft web site. You need to install all of the latest Microsoft Windows hotfixes prior to installing the Administration client. For information about which hotfixes to install, see http://www.microsoft.com/downloads/details.aspx?FamilyID=7554F536-8C28-4598-9B72-EF94E038C891&DisplayLang=en.
Hope this helps.
Regards,
Poonam

Problem opening BEx Analyzer Workbook (saved in Excel 2007) in Excel 2003!!

Dear all:
I know there are threads about this issue and numerous support tickets have been provided, but we still can't get any Excel 2007 Query to be opened by Excel 2003.
I have tried to save Excel 2007 BEx Analyzer Query into 97-2003 XLS format. But when we reopened (by both Excel 03 and 07), it prompted the warning messages and broke down the query workbook into several sheets with scrambled data. What am I missing here...? According to the support ticket, it seemed pretty straightforward just by saving the format to 2003 XLS, but in reality it just doesn't work as "advertised"
Thank you...!!!
Brian

I have the solution for this.
It works to my environment.
Follow the steps :
1. you must open the xlsx workbook from Bex Analyzer.
2. Save As workbook locally to your PC for excel 97-2003
(Not "save as" from bex Toolbar but from excel)
3. Now save that workbook with Save As->Workbook from Bex Toolbar into your BI database.
Now go to detail properties of your workbook and there you can see the format xls for your workbook.
Good Luck

BPC 7 : Excel 2003 and Excel 2007 Conflict

Hi Experts,
I have created a template in BPC 7 MS on my computer which has Excel 2003 version.
But when I try that template on another computer which has Excel 2007. The format (in the format Range) did'nt seem to work or it has diff effect on Excel 2007.
Is there really a conflict between them?? and cannot have different Microsoft Office version?? Or is there An Add-on that we have to Install so that Excel 2003 and Excel 2007 can be used at the same Time??
Thanks,
Bennie Jay

Sorin:
Situation
I also have the same issue with Excel formatting in Excel 2007, and I found a work-around specifically to my issue.
At the format section's CRITERIA, I have one entry: HEADING="New Budget" in the Column direction, apply certain color and number format to the cells of that column. However, I used Excel function CONCATENATE("HEADING=",EVDES("FINANCE",CATEGORY)) to come out with HEADING="New Budget", rather than just typing the string value.
With the above exercise, in Excel 2003 the format would apply no problem, but in Excel 2007, the entire formatting went wild and broke. After I dropped CONCATENATE() and just typed in HEADING="New Budget", the formatting applied OK in 2007.
Data
We are currently on BPC 5.1 SP5
The original report was built in Excel 2003
Question
Is there a setting in Excel that would allow me or bypass the restriction to use Excel functions to come out with CRITERIA definition?

Slow query performance in excel 2007 vs excel 2003

Hi,
Some of our clients recently did an upgrade towards BI 7.0 and also upgraded towards excel 2007.
They experience lots of performance problems when using the Bex analyser in excel 2007.
Refreshing queries, using 'simple' workbooks works till 10 times slower than before using excel 2003.
Has anyons experienced the same?
Any tips/tricks to solve that problem?
With regards,
Tom.

Hello all,
1) Please set the following parameters to X in transaction
    RS_FRONTEND_INIT and check the issue.
Parameters to be set are
ANA_USE_SIDGRIDDELTA
ANA_USE_SIDGRIDMASS
ANA_SINGLEDPREFRESH
ANA_CACHE_WORKBOOK
ANA_USE_OPTIMIZE_STG
ANA_USE_TABLE
2) Also refer to below KBA link which would help to resolve the issue.
   1570478 BW Report in Excel 2007 or Excel 2010 takes much more time than
3) In the workbook properties please set the flag
     - Use Compression When Saving Workbook
4) If you are working with big hierarchies please try to improve
performance with following setting directly in AnalysisGrid:
   - Properties of Analysis Grid - Dispay Hierarchy Icons
   - switch to "+/-"
Regards,
Arvind

? Office 2013 to support Excel 2003 (XLS) spreadsheets containing VBA CommandBars references

Thanks in advance for reading this and offering any wisdom you have! I am not an expert in any of the following, so apologies if off base.
The basic problem is: I need to use Excel 2013 to support Excel 2003 (XLS) spreadsheets containing VBA 'CommandBars' references which don't seem to work in Excel 2013. Details below.
Most of our users are still using older desktop windows PCs and Office 2003! We are beginning to upgrade to laptops running Windows 8.1 with Office 2013. Of course, we IT technical people are using the new laptops first. These new laptops are
64 bit.
Years ago, someone did a lot of development with spreadsheets here in Excel 2003 file formats that automates many activities and routines. Now we with the new laptops are having to support this development using new machines.
There is a basic compatibility issue that appears when first opening these Excel 2003 files that have VBA code that I'll detail below; I seem able to get by that problem.
The current problem appears to be that the existing Excel 2003 VBA code has many references to: "For Each bar In Application.CommandBars". As I've learned, the Application.CommandBars VBA functionality is focused on older MS Office versions' menu
commands, but "...Starting from Office 2007 the Fluent UI is used instead." In other words, because MS Office isn't menu-driven beginning with version 2007 (uses 'the ribbon'), it appears that these references to: "For Each bar In Application.CommandBars"
create a basic incompatibility to opening these spreadsheets in Office 2013.
For a spreadsheet, after I resolve the issue detailed below and save it, when I reopen it I encounter error "Compile error: can't find project or library."
For example, the following code snippet:
Private Sub Workbook_Open()
For Each bar In Application.CommandBars
bar.Enabled = False
Next
results in: "Compile error: can't find project or library."
(Sorry, can't include images yet, I am not a VERIFIED USER of this forum yet.)
I went into VBE's menu: Tools>References and check for anything marked MISSING, which I deselected. But I am still receiving this error.
I don't want to get into changing the code a lot to support both Excel 2003 and 2013 (I am no VBA expert, just a dabbler).
And Microsoft officially says that Office 2003 is incompatible with Windows 8 although Application.CommandBars seem to be somewhat supported in Office 2013 .
Are you aware of a quick VBA workaround to get by this?
•I could comment out the validations, commands for: "For Each bar In Application.CommandBars" but then the spreadsheet code probably won't work for users using Office 2003.
Alternatives would be:
•Installing Office 2003 on my Win 8.1 64 bit laptop anyway, in spite of MS's saying incompatible, since this thread discusses at least one person has been able to use Office 2003
•Keeping one older PC with Office 2003 on it for us to support the old Office 2003 code until everyone upgrades their systems
Thanks
Basic compatibility issue that seems solvable:
Opening these spreadsheets displays this error:
Compile error:
The code in this project must be updated for use on 64-bit systems.
Please review and update Declare statements and then mark them with the PtrSafe attribute.
This seems resolvable by going into the VBA code and just adding element 'PtrSafe' where functions are declared; in other words, replacing VBA code "Declare Function" with "Declare PtrSafe Function" seems to get by this.

Hi Allan_L,
Please try the methods that provided above. And this is the forum to discuss questions and feedback for Microsoft Excel, your issue is related to Excel DEV, if you have further question, I recommend you post the question to the MSDN forum for Excel
http://social.msdn.microsoft.com/Forums/en-US/home?forum=exceldev&filter=alltypes&sort=lastpostdesc
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Printing Excel Instance from InfoView using Excel 2003

Hi
I have problem with printing Excel instance within InfoView. We are using Active X as viewer - but when user schedules report in Excel and when it opens that instance - it opens in Web Excel viewer within InfoView. At that point there is no standard menu if user uses Office 2003 or actually Excel 2003 on its own machine so user cannot print instance. Can anybody help with this. If you try to open instance on machine that has Office 2007 there are no problems since instance gets open in full Excel.
Thanks

What version of Crystal Reports are you using? Any service packs or hot fixes installed?
Can you open other xls files with 2007?
Have you ever exported to excel before?
I export to -excel (97-2003) data only- and open the files with Excel 2007 with no problems. Excel 2007 complains about the old format (xls) and wants to convert it to the new excel format. I alsways ignor it.
Maybe the 'garbage' you are seeing is because the layout of your crystal report is not working for the export. Is all the data there but you have extra cells and/or lines, or the data is pushed to the left? I find that I must have the fields packed tightly with no space between them and no space above or below the fields, or I get extra cells between and lines above or below them.
Most of my exports are detail lines with a single line header and columns are set to match the detail line. When exporting multiple lines where the fields do not line up exactly with the ones above them, I may use one or more empty text fields that matches the size of the fields above them to fill the empty space. Sort of like:
line 1:{field1.}{field2...}{field 3}
line 2:(text...}{text.....}{field 4)
And you may need to turn off 'can grow' on all fields as they may cause miss-alignment. All the data will be there when you export it, even what you can not see in Crystal. You will just need to format the cells in Excel to see it.
Debi (hi Don)

Report Generation Toolkit with Excel 2003 and Excel 2000

Hello,
I'm using the Report Generation Toolkit to generate an Excel report from an Excel template.
The "NI_Excel.lvclass" is included in the "source" section of the application builder options.
I create an exe file on a PC where Excel 2003 is installed. On a Notebook, where only Excel 2000 is installed, the application crashes at the generation of the report:
I guess the problem is the different version of Excel but I don't know. On the developer PC with Excel 2003 it works fine.
In this document it's only talked about different Word versions.
How can I use the Report Generation Toolkit here?
I'm using it that way:
Regards

Oh, it seems that the Report Generation Toolkit "only" supports Excel XP/2003/2007.
I think, that's the problem.

I can't transfer data properly to Excel 2003 with the report generation toolkit.

I have a table with number to transfer into Excel. I use EasyGraph.vi and it works correctly with Excel 2000. But when I try the same program to transfer my data into Excel 2003, the data are not transfered correctly. When I have for example 0,56, it is read as text in Excel and when I have something like 53,300 Excel 2003 read this 53 300 as if there was no coma.
Do you know what's happening with Excel 2003 ?

Separators have always been a pain in Excel !
A work around is to avoid using any separator at all, and to format numbers as power of 10.
For instance :
0.12345 -> 12345E-5
12.345 -> 12345E-3
The attached vi does the trick.
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...
Attachments:
NoSeparatorEnumbers.vi ‏20 KB

Numbers to Excel (2003 or 2007)

Similar Messages

Maybe you are looking for