BO 6.5 - save as excel 2003 (problem date 31/12/2099)

hi,
i've a query result in BO with a date "31/12/2099". This date come from an oracle db file.
I save it into xls (save as) but the result in xls give me "30/12/1900".
With other date, there is no problem.
an idea to correct this ?
thanks

A workaround for this issue is to select the entire document, go to Edit > Copy All, and then paste it into an Excel spreadsheet. You will get the correct dates and the table will remain in the same format as the original *.rep document. You can then do further calculations in the Excel spreadsheet.
Note: If the *.rep document contains gaps, then they will not be pasted into the Excel spreadsheet unless you use "Paste Special". If you do this, then you will be able to view the data but you will not be able to do further calculations in the Excel spreadsheet.
Regards,
Sarbhjeet Kaur

Similar Messages

Excel 2003 problem with group policy

When I manually install EMET Excel 2003 works. When Emet is installed via Group Policy Excel 2003 fails to open. Excel 2010 works whether EMET is installed locally or with Group Policy. Any ideas?

I would try exporting the policy on both installs using emet_conf --export and comparing the 2 policies
GBS Premier Field Engineer Cybersecurity Check out my blog http://blogs.technet.com/kfalde or better yet check out http://technet.com/wiki and start contributing :)

Excel 2003, 2007 data recovery

Hi Friends,
A folder containing lot of excel files (.xls & .xlsx) had been deleted from my drive which I had retrieved back from the hard-disk. But out of these few files had been corrupted.
When I open the file, it displays an error ---
1) "Excel cannot open the file 'FileName.xlsx' because the file format or file extension is not valid. Verify that the file has not been corrupted and that the file extension matched the format of the file".
2) "Excel found unreadable content in 'FileName.xls'. Do you want to recover the contents of this workbook? If you trust the source of this workbook, click yes". When clicked Yes it displays - "Unable to read file". Again when clicked ok - "The workbook
cannot be opened or repaired by Microsoft Excel because it is corrupt"
Please help me on recovering the datas of all the corrupted .xls & .xlsx file, solving these kinds of error.
Best Regards, Raj

The best way is to find another copy: backed up someplace, emailed copy, co-worker/boss, at home.
Alternatively, the OpenOffice/LibreOffice programs can sometimes open corrupted .xls files (some say).
Both programs are free, but are very large downloads. If you try one of them, please post back with your results.
Jim Cone
Portland, Oregon USA
http://www.mediafire.com/PrimitiveSoftware
(Formats & Styles xl add-in: lists/removes unused styles & number formats - in the free folder)

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

Excel Readpage Save as another file problem

Hi,
I have attached the VI needed If you have any problems please let me know. This VI reads a excel page the user points to and displays the results. I have added a single cell where you can change the position of a single cell coordinates so that you can point to a single cell of your choice and retrieve that data. So my problem is now I want to save that data from that single cell to ANOTHER excel file. However, this is not working correctly for some reason I do not know why I believe I have done everything correctly hopfully it is just my inexperiance. I will continue to work on this and update it as I get more time but at the current moment I have hit a brick wall. I have visited the EXCEL BOARD and the vi is from there but I had to add somethings to it in order for it to work correctly as before it wouldn't even run because it was missing some connections and nodes.
Attachments:
ExcelReadPage.vi ‏45 KB

I took a look at the toolkits. The VIs are there, the problem is that
the linkages are a bit screwed up so the top-level VIs think the subVIs
are in different places. Also, the toolkits were written using an
older version of Excel, in which the "Range" object had the property of
"Value". Excel 2003 uses "Value2". So, if you have Excel 2003 even
after you load up the VI the "Value" property nodes need to be changed
to "Value2". This is not a fault of the toolkits - this is due to
Microsoft changing the ActiveX interface.
As to your issue: Your basic steps are to:
Create a new workbook
Write values to cells
Save workbook
The "Write Table to XL" that ships with LabVIEW does that. Launch the Example Finder (Help -> Find Examples) and search for "excel". Then, open the "Write Table to XL". The "Table" control is the data that you want to write. It can be a single cell or multiple cells. If you have a single value, just make a 2D array out of it. As it's written it will prompt you if you want to save the file. This is from the "Close" method. You can wire a True constant to the "SaveChanges" parameter and a path to the "Filename" parameter.

Excel Analyzer template problems with Excel 2003

There are numerous common problems when using Excel Analyzer templates with the Analyzer Add-In for Excel 2003:
The following problems have been found in the latest version of the stand-alone BI Publisher version 10.1.3.3.2:
1) If your report name is more than 24 characters long, the Excel Analyzer template will never open in Excel. The error is completely uninformative, too. The reason is that the Analyzer template tries to make a tab in the Excel file called <report_name>.xdo. Since tab names can only be about 26 characters long, Excel chokes when opening the file. It would have been nice if BI Publisher printed an error when encountering this situation.
2) If your report produces too many rows, Excel will time out when opening the Analyzer template. Again, the error in this case is completely uninformative. In fact it appears no different from the error in (1). Excel 2003 is supposed to have a row limit of 65,000, but we can't get the Excel Analyzer template to open with more than about 15,000 rows. This is a completely unacceptable limitation if you're going to be making pivot tables in Excel. This is a processing time-out problem, which cannot be remedied by changing any settings in BI Publisher.
3) If you use the data in your Excel Analyzer template to make a wide report, like maybe one column for each day in the year, because maybe you want to plot the data over a full year, then forget about opening this report successfully. Since the number of days in a year is more than 256, Excel will choke when trying to open the template. No informative error here either.
4) If you're going to make a Pivot Chart in Excel, in the Analyzer template, then your reports cannot produce more than 256 rows. I'm not talking columns, I'm talking ROWS people! No more than 256 rows. This is because Pivot Charts require creating a sideways pivot table, which means your rows end up as columns. This is the only way to plot data with time on the x-axis, which is where it should almost always be.

I posted the link to the Microsoft software that works with Office 2007 to save as a PDF
If you need other Microsoft help, search at http://search.microsoft.com/search.aspx?mkt=en-US&setlang=en-US
If you have a Reader question, go to http://forums.adobe.com/community/adobe_reader_forums

PDFMaker 9.1, Excel 2003, Users can't save form data

Hi Everyone,
I'm looking for some assistance with a problem.
I created a new form in Adobe Pro 9.1 bringing in an excel template. The final product looked great. I had our IT department post it on our Intranet, and some individuals commented back they cannot save a copy of the data they entered in the blank form. I tested with others where it works fine. I can't confirm 100%, but it seems whoever has the Adobe "Pro" version can save and those with just the "standard" cannot save. They get that message Save a Blank Copy of this Form, Data typed into this form will not be saved..."etc.
I tried going to Advanced-Extend Features in Adobe Reader, but that doesn't help either once posted on the website.
Any suggestions how to enable so that all users (1000's) can save their work they typed into the document if they wish?
Thanks so much in advance!

Not specifically addresses whatever is causing the issue.
Just an obtw re: "extended" PDF forms (which, if there are users of Adobe Reader, will have to be made use of):
When you "extend" a PDF form usage most comply with the "500 limit" of the EULA.
With "1000's" of end-users you may well be in harms way.
See Section 15.12.3 (PDF page 408 of 410).
http://www.adobe.com/products/eulas/pdfs/Gen_WWCombined-20080205_1329.pdf
LiveCycle ES avoids this but is costly.
Alternatively, piping out the user's form input to FDF and processing that at the server level could be done.
For this, you might have your IT folks give the FDF SDK a look over.
Be well...

BO 6.5 : save as excel (problem date)

hi,
i've a query result in BO with a date "31/12/2099". This date come from an oracle db file.
I save it into xls (save as) but the result in xls give me "30/12/1900".
It is the same for date greater than 31/12/2099.
for date < 1900 the result is 01/01/1900 !!!!
I think the problem is to resolve the date in two positions (YY) to four positions (YYYY)
is it possible to bypass de transformation ?
an idea to correct this ?
thanks
Edited by: dlbank on Jun 22, 2009 1:43 PM
Edited by: dlbank on Jun 22, 2009 1:45 PM
Edited by: dlbank on Jun 22, 2009 1:47 PM

Hi,
Following solution might be helpful in resolving the issue.
A workaround for this issue is to select the entire document, go to Edit > Copy All, and then paste it into an Excel spreadsheet. You will get the correct dates and the table will remain in the same format as the original *.rep document. You can then do further calculations in the Excel spreadsheet.
Note: If the *.rep document contains gaps, then they will not be pasted into the Excel spreadsheet unless you use "Paste Special". If you do this, then you will be able to view the data but you will not be able to do further calculations in the Excel spreadsheet.
Regards,
Sarbhjeet Kaur

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

Anyone seen this problem with Excel 2003?

We're developing a Microsoft Excel-based app. The help system uses HTML Help (.chm) format, and works just fine with Excel 2007 and 2010. However, since a lot of potential users out there are still using older versions, we've been asked to adapt the app for Excel 2002 and 2003.
The help system works, more or less, with Excel 2002, but when we try it with Excel 2003 the tri-pane is missing. The default topic appears but the left-hand pane containing the navigation system (TOC, Index and Search) is missing. Consequently, users can't move away from the default topic. Has anyone come across this problem before, and do you know how to fix it?

I cannot help you with this one other than to say I haven't seen any other such reports. That may suggest it is worth checking for some small difference you haven't identified yet.
Of course it could also mean there aren't many people with that workflow.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Problems embedding PDF files into Excel 2003 workbooks

Several of my fellow consultants engaged on a client project were previously able to successfully embed PDF files as objects within Excel 2003 workbooks. However, most recently, a few of them have been encountering odd icon displays for the embedded object (not the standard Adobe PDF icon), resulting in the user unable to view the object (these colleagues are using desktop PCs running Excel 2003 and Adobe Reader 9.3.2). Has anyone encountered this and have a remedy?

Thanks for responding -
My colleagues report that no error messages appear when adding the object to the Excel spreadsheet - however, the object is created with a non PDF icon being displayed. Once the icon is double clicked, nothing appears. The sample of the problem was forwarded to me - where I can see that the object icon is in fact a non Adobe PDF icon (see below). While I am able to open the PDF file with my PC desktop configuration (Windows XP, Excel 2007, Adobe Reader v9.4.1.), those with Windows XP, Excel 2003 and Adobe Reader v9.3.2 can not. Any thoughts?

Problem displaying Web charts via Excel 2003

Hello,
While displaying a Web template via a hyperlink in <b>Excel 2003</b> (the hyperlink contains the template's URL), all charts in the template aren't displayed. The small red x appears in the chart's area. Charts are displayed only after refreshing the browser.
Same scenario works fine with Excel XP !!!
No problem occures when openning the same URL directly in the browser, so I guess the problem relates somehow to the hyperlink.
Any ideas?
Thanx.

Strange...
I can think of a hack: Have an intermediate html page that gets displayed first anytime the display type (html/xls) is changed. Just a blank html page with a redirect that directs to the source you really want to display.
Should be transparent, and it should clear up your problem as you described it.

ActiveX Save As function for Microsoft Excel 97- Excel 2003 & 5.0/95 Workbook (*.xls)

Can someone show me how to use Active X - Save As function?
I want to save it in Microsoft Excel 97- Excel 2003 & 5.0/95 Workbook (*.xls)
thanks in advance!
Best regards,
Krispiekream
Solved!
Go to Solution.

Oh,
I thought people stopped reading my other post so I posted another.
sorry.
but i found the solution
FileFormat variant name integer code
Microsoft Excel Workbook xlWorkbookNormal -4143
Web Page xlHTML 44
Template xlTemplate 17
Text (Tab Delimited) xlCurrentPlatformText -4158
Unicode Text xlUnicodeText 42
Microsoft Excel 5.0/95 Workbook xlExcel5, xlExcel7 39
Microsoft Excel 97-2000 & 5.0/95 Workbook xlExcel9795 43
CSV (Comma Delimited) xlCSV 6
Microsoft Excel 4.0 Worksheet xlExcel4 33
Microsoft Excel 3.0 Worksheet xlExcel3 29
Microsoft Excel 2.1 Worksheet xlExcel2 16
Microsoft Excel 4.0 Workbook xlExcel4Workbook 35
WK4 (1-2-3) xlWK4 38
WK3, FM3 (1-2-3) xlWK3FM3 32
WK3 (1-2-3) xlWK3FM3 15
WK1, FMT (1-2-3) xlWK1FMT 30
WK1, ALL (1-2-3) xlWK1ALL 31
WK1 (1-2-3) xlWK1 5
WKS (1-2-3) xlWKS 4
WQ1 (Quattro Pro/DOS) xlWQ1 34
DBF 4 (dBASE IV) xlDBF4 11
DBF 3 (dBASE III) xlDBF3 8
DBF 2 (dBASE II) xlDBF2 7
Formatted Text (Space Delimited) xlTextPrinter 36
Text (Macintosh) xlTextMac 19
Text (MS-DOS) xlTextMSDOS 21
CSV (Macintosh) xlCSVMac 22
CSV (MS-DOS) xlCSVMSDOS 24
DIF (Data Interchange Format) xlDIF 9
SYLK (Symbolic Link) xlSYLK 2
I know that its saving in the correct format. BUT I don't know why it wouldnt save 2 worksheets, but instead it only have 1.
Best regards,
Krispiekream

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

Printing problem Adobe Pro X from Excel 2003

I produce a number of reports each month using Excel 2003 and printing/converting them to PDF documents. All were nicely formatted and printed perfectly and reliably using Adobe 5.0 (ancient I know). I recently upgraded to Adobe Pro X. Now what once printed nicley only prints part of a page - about the right 1/3 is not showing. Even when selecting "fit to 1 page wide and 1 page tall" in excel page setup doesn't fix the problem. Changing the BINDING setting in Adobe doesn't fix the problem either. Previously I selected Adobe Writer from my printer listing which I understand has been discontinued. Now my only option is Adobe PDF. Any suggestions?

Interesting. My approach would
1. Try on a different system if available. If still bad...
2. Try to create a simple test application with CreateDC and StartDoc, and really nothing else not absolutely needed.
Test that. If it is good, look for other problems in your application (e.g. memory overwrite).
If your little example is still bad, post it here and other people can try and compare your results.

BO 6.5 - save as excel 2003 (problem date 31/12/2099)

Similar Messages

Maybe you are looking for