Troubleshoot Document Manager and Productivity Components

 

+
Search Tips   |   Advanced Search

 

---

Contents

1. Loss of unsupported features upon document conversion
   • Document Viewer
   • Rich Text Component
   • Spreadsheet Component
   • Presentation Component
2. Problems viewing documents as HTML
3. Problems with Document Conversion Services
4. Problems with SearchML
5. Known limitations for Productivity Components
6. Known limitations for Document Manager
7. Using Netscape and Opera browsers with Document Manager and Productivity Components

 

Loss of unsupported features upon conversion

Productivity Components can view and edit many document formats via the document conversion framework. As with any document conversion, however, some loss of formatting and features is expected.

The following list details some reasons why documents opened in Productivity Components do not retain all of the features of the program they were created in:

• The source document uses features not available in Productivity Components. For example: OLE embeddings are dropped when loading certain spreadsheets in Productivity Components.
• Conversion from the source document to the target document requires a lossy conversion. For example: vector graphics might be converted to bitmaps on the server.
• The source application has more formatting and styling options than Productivity Components.

 

Document Viewer

The viewer makes a read-only HTML rendering of the source document. The business information of the source document should be preserved, though the styles and formatting might diverge from the original. In particular, graphical file formats, such as Freelance Graphics or PowerPoint, render as JPEGs, one per slide. This conversion relies on the graphical capabilities and settings on the server, including:

• available fonts
• resolution
• color depth

For best results, users should ensure that the server has the same fonts available as used in the source documents, and that the color depth of the server matches that of the majority of the clients.

 

Rich Text Component

The rich text component uses HTML as its document format. The following features are lost in conversion:

• Page-level constructs, such as headers, footers, page numbers, and hard page breaks are not part of HTML. So page breaks will be lost and repeating page-level text, such as headers and footers, will be inline on each page.
• Graphics within text blocks can change position, since the ability to position graphics within text blocks is more constrained in HTML than in full-functioned word processors.
• Text control depends on which client browser you use. These controls differ in the details of text layout, especially with regards to complex tables.
• Client differences, especially across a heterogeneous client platform base, can effect fidelity, especially with regards to available fonts.

 

Spreadsheet Component

Productivity Components' spreadsheet component supports a single worksheet with styled cells and text and numeric entries with the most common formats. When converting a spreadsheet file to Productivity Components, expect the following degradations:

• Only the first worksheet of the workbook will be converted.
• Platform-specific features are dropped, for example: OLE embeddings, macros, etc.
• If an unsupported style or format is used in the source document, it will be converted to the closest matching style/format. For example, double underline cell style is converted to single underline.
• If a function in the source document is not available in the Productivity Components editor, Productivity Components flags that cell as an error when the document loads.
• Named ranges in the source document are not supported.
• Formulas referring to other document files (links) are not supported.

 

Presentation Component

Productivity Components' presentation component supports a slide show of multiple slides contained JPG/GIF images, text blocks, bullet items, rectangles, and horizontal and vertical lines. When converting other presentation file formats, you will see the following:

• Platform-specific features are dropped; for example: OLE embeddings.
• Page and object transitions, such as animation, are not supported.
• Embedded sound clips are not supported.
• Only raster graphic formats, such as JPEG and GIF, are converted. Vector formats, including all custom charting/drawings done within the previous presentation editor, are dropped.
• Since the Productivity Components presentation component does not support Author notes, these are dropped.
• Productivity Components' presentation component does not support multilevel text styles, so these are dropped.

Therefore, a presentation author who uses who wishes to create content for viewing in Productivity Components but creates the file in another presentation editor should avoid the standard presentation master templates of those products. If the author wishes to use a master template, he or she should use a template with raster graphics, simple, solid backgrounds, and bullet items decorated with GIF line art and/or JPG clip art.

---

 

Problems viewing documents as HTML

Certain file types can be viewed as HTML in Document Manager. If you are having problems viewing a document as HTML, refer to the Viewing documents in HTML topic for a list of supported file types.

A Presentation Editor file viewed in HTML view does not display bullets correctly and all text displays the same size.

---

 

Problems with Document Conversion Services

Problem: You might receive the following warning when using WinZip 9.0 to open remotedcs.zip on Windows:

Warning: the size of the extracted file (28509) does not match the uncompressed size (0) recorded in the zip file.

Solution: Use an archiving utility other than WinZip.

Problem: After adding Open Office file types to the content-types.properties file, and importing Open Office Writer files, cannot preview these files in Document Manager.

Limitation: Document Conversion Services only supports indexing of Open Office documents. Previewing in Document Manager is not supported.

---

 

Problems with SearchML

1. Page number in Open Office will not be reflected correctly in SearchML, after conversion.

2. Double Byte Code Set characters in SearchML are illegible after conversion from Open Office-Calc

3. Currency format of financial function in Open Office will not be reflected correctly in SearchML after conversion.

4. Header and footer in Open Office will be lost in SearchML after conversion.

---

 

Known limitations for Productivity Components

1. Change session timeout for Productivity Components
2. Productivity Components not supported in a Tivoli Access Manager authentication environment
3. All Components
4. Presentation Component
5. Rich Text Component
6. Spreadsheet Component
7. Internet Mail Box

---

 

Problem: Changing session timeout for Productivity Components

The default LTPA Token timeout is two hours. This might be different from the portal session timeout. If the Productivity Components need to function longer than two hours, then extend the LTPA Token timeout through the WebSphere Application Server.

---

 

Problem: Productivity Components not supported in a Tivoli Access Manager authentication environment

The Productivity Components (Rich Text, Spreadsheet, and Presentation) are not supported in a reverse proxy environment such as Tivoli Access Manager authentication environment.

Solution: This is a known issue and will be fixed in a future release.

---

 

All components

• Cannot save a file after conversion if Workflow is enabled
• No content displayed after clicking hyperlink in Help in some locales
• Productivity Components for Korean locale might not display correctly

 

Related to Mozilla

• No progress window shows when creating or loading a file into one of the components
• Japanese Yen sign does not always display correctly using Mozilla on Linux

---

 

Problem: Cannot save a file after conversion if Workflow is enabled

If you have an Excel, Word, or PowerPoint file and you try to edit the file, a conversion occurs so the file can be manipulated in the corresponding Productivity Component. When you then try to save the file, a message displays that the save failed.

Solution: Before the file can be saved, the task that was created in the tasks folder for the conversion of the file to the Productivity Component format needs to be approved by the reviewer. Once the task has been approved by the reviewer, the author will be able to save the document.

---

 

Related to Mozilla

 

Problem: No progress window shows when creating or loading a file into one of the components

When a rich text file, spreadsheet file, presentation file or Internet Mail Box e-mail is created or opened for editing using Mozilla 1.3, the file will load in a background window until the loading operation completes. The component window then will appear in the foreground.

This is a focus issue with Mozilla when both the portlet window and the component window are refreshing. The focus does not move to the component window until the loading in the portlet window completes.

Solution: Wait for the file to load and the focus will correctly return to the opened component.

---

 

Problem: Japanese Yen sign does not always display correctly using Mozilla on Linux

The Japanese Yen sign does not always display correctly and a backslash might be displayed instead.

Solution: Tahoma font works best for all components.

---

 

Presentation component

• Inconsistent behavior for Cut, Copy, and Paste icons
• Link breaks between the title and outline
• Cannot print first page with wood or ruled image background
• Cannot view pictures in Presentation Component while in Document Manager
• Cursor not visible after clicking in a new bullet text block
• Leading space or space between words disappear when cursor moves
• Bolding in title disappears after conversion
• Bullets disappear when aligning text

 

Related to Mozilla

• Cannot see first line of text in bulleted list while typing
• Cannot paste items in correct spot
• Difficulty editing text items
• Cannot edit a page in Outline view
• (AIX only) Color dialog box does not display

---

 

Problem: Inconsistent behavior for Cut, Copy, and Paste icons

In Presentation Component, the Edit>Cut, Edit>Copy and Edit>Paste icon behavior might differ from the equivalent keyboard function.

When you use the icons, the information is cut, copied, or pasted to the browser clipboard whereas when you use the keyboard functions, the information is cut, copied, or pasted to the system clipboard.

Solution: A possible workaround is to use ctrl+c to copy and ctrl+v to paste the text into the frame.

---

 

Problem: Link breaks between the title and outline

In Presentation Component, if you delete the default title in the outline view, the link between the title and outline view is broken. When the title frame is copied, it is converted to a text frame which can be used anywhere in the page. However, this prevents it from becoming a title frame in the new page.

Solution: Manually enter the text in the outline either by cutting and pasting or by typing it in.

---

 

Problem: Cannot print first page with wood or ruled image background

In Presentation Component, there is a timing issue concerning the browser. If you are using a remote server and the wood image as the background image, the first page does not print correctly.

Solution: Choose a different background image.

---

 

Problem: Cannot view pictures in Presentation Component while in Document Manager

In Presentation Component, files that include linked pictures cannot be viewed when clicking on the file in Document Manager. Images inserted as background images and Master styles selected in Presentation Component are not displayed in the HTML file.

Solution: There are two ways to insert a picture in Presentation.

1. You can upload a picture from the local file system. These pictures can be viewed in the Document Manager.
2. You can also link to a picture on a Web server by using a URL link. The picture will display correctly in the Presentation but cannot be viewed in the Document Manager.

---

 

Problem: Cursor not visible after clicking in a new bullet text block

In Presentation Component, after you have created a bullet text block, the cursor disappears. If you enter text, the cursor will appear but in the wrong place.

Solution: Click outside the bullet text block and then click back in that block. The cursor returns to the correct block.

---

 

Problem: Leading space or space between words disappear when cursor moves

In Presentation Component, when you move the cursor to another place in the file, the leading space or the space between words disappear.

Solution: Move the cursor back to the line and the spaces return.

---

 

Problem: Bolding in title disappears after conversion

After converting a Presentation Component file to a PowerPoint file, you might lose the bolding in a title.

Solution: In the Presentation Component file, change the title to normal text. Then change the title to bold again. Then you can covert the file again, and the title will remain bolded.

---

Limitation in Presentation
Bullets might disappear when editing if the bulleted text is centered or right-aligned.
After converting a file from Lotus Freelance Graphic to Presentation Editor, the following changes might occur: Text features such as font styles, font size and font color are changed Bullets are changed Master stylesheet is changed An image such as a screen capture becomes blank Textbox size is smaller A graphic file larger than 1.28 MB becomes blank Table cells become divided into small rectangles
After converting a file from Presentation Editor to Lotus Freelance Graphic, the following changes might occur: Font sizes are lost Text fonts are changed Hyperlinks are lost Master styles change Background color changes Sometimes the color stays on the same on Windows machines. Images are lost
After converting a file from Microsoft PowerPoint to Presentation Editor, the following changes might occur: Text content with plain, bold, italic, underline, or a combination of bold, italics and underlining with left, right and center alignment is lost Rectangle background color changes, for example, green changes to blue Hyperlinks are changed to plain text A blue border appears around any textboxes Master stylesheet is lost Tables become textboxes Dates become asterisks

---

 

Related to Mozilla

 

Problem: Cannot see first line of text in bulleted list while typing

In Presentation Component, if you have a line in a bulleted list that wraps to the next line, you cannot see the first line of text you just entered.

Solution: If you click outside the text box, all the text will appear.

---

 

Problem: Cannot paste items in correct spot

In Presentation Component, if you have a cursor in the beginning of a sentence and you paste in a word, the word is not placed before the cursor in front of the sentence but gets copied to the next line.

Solution: A workaround is to use ctrl+c to copy and ctrl+v to paste.

---

 

Problem: Difficulty editing text items

In Presentation Component, you might have difficulty editing text with small fonts. For example, those of 12 point or less.

Solution: Either increase the size of the fonts or click outside the boundary of the text box.

---

Limitations in Presentation on Mozilla
(AIX on Mozilla only)If you go to Page > SetBackground, the Select a Background Fill color box does not display.
If you double-click on a page in the Page Sorter view, you are not able to edit the page in Outline View.

---

 

Rich Text Component

• Using Format drop-down menu changes all words in a line of text
• Font type and font size is not displayed
• Hyperlinks do not work in edit mode
• Numbers in numbered list do not display correctly
• Cannot cut highlighted text across cells in a table
• Characters with extended formats might be lost
• Double Byte Character Set font specified in WordPro file not reflected
• Cannot save files while in source mode
• Cannot convert from Rich Text Component to SearchML or WordPro to Rich Text Component
• Cannot input Chinese (zh_CN and zh_TW) characters using Input Method Editor in Rich Text Editor
• Receive error message when converting a password-protected file
• Bulleted list must be indented one level

 

Related to Internet Explorer

• Choosing the Normal heading in Format inserts HTML tags around lines
• Tab does not indent
• Pressing Enter does not work with the image dialog box
• Cannot select a table to delete

 

Related to Mozilla

• Closing the window using the button in the upper right corner
• Can drag and drop toolbar icons into a document
• Cannot select a table to delete
• Cannot undo the insertion of a table.
• Problem with deleting characters in a table
• Cannot remove underlining in a table
• Entire list does not bold
• Trouble inserting a URL
• Difficulty cycling through keyboard accessibility functions

---

 

Problem: Using Format dropdown menu changes all words in a line of text

In Rich Text Component, using the Format dropdown menu changes all words in a line of text regardless of what is selected in the line of text. This is by design.

Solution: If you want to change the text format in part of a line, use the font or size functions instead.

---

 

Problem: Font type and font size is not displayed

In Rich Text Component, after choosing a new font, size, or heading for highlighted text and moving the cursor to a different selection of the text, and then returning, the information relating to format is not displayed on the toolbar.

Comments: This is a limitation of the browsers iFrame editable design.

---

 

Problem: Hyperlinks do not work in edit mode

In Rich Text Component, when you are editing a document, the hyperlinks do not work.

Solution: To follow a link, be in view mode.

---

 

Problem: Cannot cut highlighted text across cells in a table

In Rich Text Component, if you highlight text and your cursor crosses the cell border, even if there is nothing in that cell, when you try to cut the selection, the highlighted text will not be deleted.

Solution: Reselect the text making sure you do not cross the cell border.

---

 

Problem: Characters with extended formats might be lost

In Rich Text Component, after you convert a Word document, characters with extended formats such as the ruby feature might be lost.

Solution: All the features of a native application are available so use a native editor instead of Rich Text Component. Select Native Editor on the Document Manager Edit panel.

---

 

Problem: Double Byte Character Set font specified in WordPro file not reflected

After converting a WordPro document with Document Conversion Services, the Double Byte Character Set font specified in the WordPro file is not reflected in new file. The default Rich Text Component font is applied to all the Double Byte Character Set characters in the converted file, while font sizes and font styles, such as bold, are reflected.

Solution: All the features of a native application are available so use a native editor instead of Rich Text Component.

---

 

Problem: Cannot save files while in source mode

In Rich Text Component, if you save a document while in source mode, when you reopen the document, the source code will display.

Solution: Do not save files while in source mode.

---

 

(Linux & UNIX only) Problem: Cannot convert from Rich Text or Spreadsheet to Presentation Editor files to other formats and vice versa through Command Line test driver.

Solution:In order to enable conversions through the Command Line, perform the following steps:

1. Export PATH=$PATH:/opt/WebSphere/AppServer/java/jre/bin:/opt/WebSphere/AppServer/java/jre/lib:
2. Export PATH=$PATH:/opt/WebSphere/PortalServer/shared/app/oiexport:
3. Export <Library Path>=/opt/WebSphere/PortalServer/shared/app/oiexport:
4. Export CLASSPATH=$CLASSPATH:<WPS_HOME>/shared/app/convertors.jar:<WPS_HOME>/shared/app/jakarta-poi.jar:<WPS_HOME>/shared/app/Export.jar:<WPS_HOME>/shared/app/wps.jar:<WPS_HOME>/shared/app/wpsportlets.jar:<WPS_HOME>/IBMTrans/lib/xerces.jar:<WAS_HOME>/deploytool/itp/plugins/org.apache.xerces_4.0.13/xercesImpl.jar:<WAS_HOME>/deploytool/itp/plugins/org.apache.xerces_4.0.13/xmlParserAPIs.jar:<WPS_HOME>/shared/app/avalon-framework-cvs-20020806.jar:<WPS_HOME>/shared/app/fop.jar:<WPS_HOME>/shared/app/batik.jar:<WPS_HOME>/IBMTrans/lib/xalan.jar:<WPS_HOME>/IBMTrans/lib/HTMLParse.zip:
5. Restart WebSphere Portal.

---

 

Problem: Cannot input Chinese(zh_CN and zh_TW) characters using Input Method Editor in Rich Text Editor

When you create a new Rich Text Editor file and open for editing, you are not able to input Chinese characters using Input Method Editor in Rich Text Editor.

Solution:Click any button or selection in the Rich Text Editor interface before you start the Input Method Editor.

---

 

Problem: Garbage characters appear in Traditional Chinese

Even if you have set title and description for simplified Chinese, garbage characters appear in Traditional Chinese.

Solution: Perform the following steps to correct this problem.

1. Login to portal.
2. Select Administration > Portal Settings > Supported Markups
3. Select HTML.
4. Click on Edit Selected Markups
5. Click on Set locale-specific setting
6. Select Traditional Chinese.
7. Click on Edit setting for selected language
8. Insert UTF-8 as Character Set
9. Confirm the settings.

---

Limitations in Rich Text
If you convert a Rich Text Editor file into a PDF, you lose the background color,
If you convert a Rich Text Editor file into a PDF, there might be some special characters in Swedish and German that do not render correctly.
If you convert a password-protected file into Rich Text Editor file, you will get an error message. Password-protected file conversion is not supported.
When you create a bulleted list, the list is shifted to the right. If you highlight and press the Remove Indent button for one item, it deletes that bullet.
In some locales, if you select text for a numbered list, a list of numbers will appear in front of the text. These numbers will be in Arabic numerals, such as 1, 2, 3, not in the locale's numbering system.
After conversion from Rich Text file to WordPro, double byte character set displays as garbage characters
Only .jpg and .bmp images can be displayed in Rich Text Editor HTML preview page.
The special characters which are stored in two bytes in Single Byte Character Set languages can not be converted from Rich Text Editor file to Lotus WordPro.
Double Byte Character Set Rich Text Editor files cannot be converted to Lotus WordPro.
After converting a password-protected Lotus WordPro file to Rich Text Editor file you will receive an error message.
After converting a Lotus WordPro file to a Rich Text Editor file, the following can occur: The text features of bold, italic, underline, or a combination of bold, italic, or underline with left, right and center alignment are lost The text features of font colors, font size, font styles and background colors are lost Hyperlinks are changed to plain text Bullets with different styles and formats and numbering with different formats are lost Drop capital letter for the beginning of the paragraph do not display in the correct line of the paragraph Table Of Authorities and Table Of Content do not function Inserted lines in a page without any content in the page are not displayed in the output file. The lines will be displayed only if they are entered between two lines of text. Multiple lines are not reflected between the two texts, only one line is displayed. Different line styles are not reflected as it was in input file. Equations are lost Background color, object, and chart are lost Comments inserted for any text are lost Page breaks are lost
After converting a Rich Text Editor file to a Lotus WordPro file, the following can occur: Space between lines and paragraphs is lost Right-alignment of paragraphs is lost Some table cell contents are lost Default bullet style changes Images are not reflected Background colors are not reflected Hyperlinks are not reflected Table properties change
After converting a Microsoft Word file to a Rich Text Editor file, the following can occur: Images are lost Diagrams displayed in reverse order Text Direction change is not reflected Single border shows as multiple borders On AIX, symbols are not converted for fonts such as 'Webdings', 'Wingdings', 'Windgings2', 'Wings 3' 'WP Hebrew David', 'Monotype Sorts', 'Botanical' and 'Marlett'. Table border color and background color is not reflected On AIX, objects inserted do not show after conversion Nested tables do not appear
After converting a Rich Text Editor file to a Microsoft Word file, the following can occur: Font size, bolding, italics, and underlining are lost Hyperlinks are lost Font colors and background colors are changed Images, bullets, and borders in a table are not displayed Font style and background colors are not reflected Images are lost Paragraphs are not reflected Bullets and numbering in a table are not reflected

---

 

Related to Internet Explorer

 

Problem: Choosing the Normal heading in Format inserts HTML tags around lines

In Rich Text Component, if you choose Normal for a heading in the Format box, it will automatically insert HTML tags.

Solution: Switch to source mode and manually edit the HTML.

---

 

Problem: Pressing Enter does not work with the image dialog box

After creating a new Rich Text document, if you use the keyboard sequence of <Ctrl+Shift+p> to bring up the insert image dialog box, tab to the Browse button and then press Enter, nothing happens.

Solution: Invoke the Browse button by pressing the space key, not by pressing Enter.

---

 

Problem: Can drag and drop toolbar icons into a document

In Rich Text Component, you can drag and drop any icon from the toolbar to a document. However, this action will cause problems with your toolbar so it is not recommended.

Solution: Do not drag and drop icons from the toolbar into your document.

---

 

Problem: Cannot select a table to delete

In Rich Text Component, you might find it difficult to select a table so that you can delete it.

Solution: To delete a table, highlight the surrounding elements and press Delete or delete the cells one by one.

---

 

Related to Mozilla

 

Problem: Closing the window using the button in the upper right corner

In Mozilla, if you use the close button in the upper right corner of the window, you might receive numerous prompts to save.

Solution: Click OK to continue until the prompts no longer appear. 79964

---

 

Problem: Problem with deleting characters in a table

In Rich Text Component, if you hold the Backspace key down, it will delete the characters in that cell, then the characters in the adjoining cells and then the cells themselves.

Solution: To delete the entire table from both the HTML source and the Rich Text Component, press the delete key again.

---

 

Problem: Cannot remove underlining in a table

In Rich Text Component, an underline cannot be removed if a table is created within a table cell. For instance, if you have a table and then create a table within a cell of the original table that has underlining in it, the new table will also have underlining in all the cells.

Solution: Select the whole cell again and then click the underline button to remove the underlining.

---

 

Problem: Entire list does not bold

In Rich Text Component, if you have a list of items, select them all, and select bold, the last item does not bold.

Solution: Select the next line, even though it is blank and the last item will become bold.

---

 

Problem: Trouble inserting a URL

In Rich Text Component, if you try to insert a URL it looks like nothing is inserted.

Solution: You have to select the text first, then insert the URL. The selected text will then be associated with the link.

---

 

Problem: Difficulty cycling through keyboard accessibility functions

Due to Mozilla's implementation of the tab key while in edit mode, you might have difficulty selecting various keyboard accessible features from the Rich Text editor.

Solution: If the tab key does not work, try using shift + Tab to select the item you want.

---

Limitations in Rich Text Component on Internet Explorer
If you hit Tab, it does not indent. Instead, the dropdown menus in the toolbar are highlighted.
If you insert a table, you cannot undo that action.

---

 

Spreadsheet Component

 

Problem: Problems displaying currency in spreadsheet

An Excel spreadsheet document that uses certain national currency formats will not display with the correct currency symbol when loaded in the Spreadsheet Component.

Solution: Apply the desired currency format from within the Spreadsheet Component. 61386f_1.RN

---

• Problems displaying currency in spreadsheet
• Logical functions such as isstring() and isvalue() do not convert correctly when exporting to Excel
• Functions small() and large() do not export correctly to Excel
• Editing Excel files with formula =Cell("ROW,A30) fails and gives #PARSE error
• Converting empty Spreadsheet Editor file results in conversion errors
• Issues after conversion
• Links disappear after file conversion
• Display of functions incorrect after conversion
• Copying the text in a cell to another cell copies all the formatting of that cell
• Cell height does not automatically adjust
• Lost formatting during cut and paste
• Cannot change Date format
• Japanese era not supported by Spreadsheet Component
• In calculator preview mode cannot edit spreadsheet
• Using the select function returns an error message

 

Related to Internet Explorer

• Currency symbols do not always display
• Country names in the currency format dialog are garbled

 

Related to Mozilla

• Using keyboard sequences for copy and paste causes application failure
• Cannot always select cells in a spreadsheet
• Math Function "Trunc" does not work
• Format stamp icon does not stay depressed
• Cannot copy text between spreadsheets

---

 

Problem: Problems displaying currency in spreadsheet

An Excel spreadsheet document that uses certain national currency formats will not display with the correct currency symbol when loaded in the Spreadsheet Component.

Solution: Apply the desired currency format from within the Spreadsheet Component. 61386f_1.RN

 

Problem: Logical functions such as isstring() and isvalue() do not convert correctly when exporting to Excel

In Spreadsheet Component, logical functions such as isstring() and isvalue() do not convert correctly when exporting to Excel.

Solution: Rewrite the formula to avoid these functions. 67022.RN

---

 

Problem: small() and large() functions do not export correctly to Excel

If a Spreadsheet Component document is created with these functions using the syntax =small(num1, num2, num3,..., n), and then exported to an Excel file, the exported file will have the wrong value in that cell.

Solution: The syntax for the large() and small() functions is not valid in Excel. The correct syntax is large(Range, n), such as =large(A1:B5,2). If you use this syntax in the original document,the conversion will work correctly. 67343.RN

 

Problem: Editing Excel files with formula =Cell("ROW,A30) fails and gives #PARSE error

In Spreadsheet Component, if you edit Excel files with the formula =Cell("ROW,A30), the operation fails and gives a #PARSE error. The =Cell() function does not exist in the Spreadsheet Component, so it cannot be converted when the Excel file is imported.

Solution: Rewrite the formula for that cell. 68389.RN

---

 

Converting an empty Spreadsheet Editor file results in conversion errors

Problem: Creating a new Spreadsheet Editor file with no contents and then converting it to a Microsoft Excel file results in conversion errors when trying to show the file preview. Instead of a preview of the document, a dialog is opened with options to Save, Open, or Cancel the preview.

Solution: Make sure the Spreadsheet Editor file has content before attempting to convert it to HTML.

---

 

Problem: Issues after conversion

There can be problems after converting a spreadsheet to or from Spreadsheet Component. For example,

• Receive error message #VALUE! or #PARSE!: After converting an Excel file to Spreadsheet Component or vice versa, you might receive an error message such as #VALUE! or #PARSE! in a cell rather than the formula.
• Background colors change after conversion: If you create an Excel file, add or change the background color, then convert the file to Spreadsheet Component, the background colors in the new file will be different from the original file.
• Euro symbol displays for pre-Euro currencies: When importing an Excel sheet which uses older (pre-Euro) currencies such as the French Franc, or Deutsch Mark, the corresponding cell will display incorrectly with the Euro symbol.
• Colors change: After conversion from Spreadsheet Component file to Excel, some colors can change in the new file. Also, some text colors (such as grey) might display text in white which is not visible.

---

 

Problem: Links disappear after file conversion

In Spreadsheet Component, if you add a Web link to a cell and click on it, you are taken to the URL or if you add a picture URL to a cell, the corresponding image is displayed in that cell. However, if you convert that file to Excel, you then see the formulas for those links, rather than the Web page or the picture.

Solution: Go to the cell with the link, hit F2 to edit the cell and then press Enter. The link will then be created.

---

 

Problem: Display of functions incorrect after conversion

If you use functions like =concatenate(),=PPMT(), or =abs(), convert the spreadsheet to or from Excel, and then click the document link to view the spreadsheet as HTML, the display is incorrect.

Solution: Click the edit icon to see the contents correctly. Alternatively, if the conversion was from Spreadsheet to Excel, download the converted Excel file and use Microsoft Excel application to view the content correctly. If the conversion was from Excel to Spreadsheet, open the document in edit mode, save, and the view is correct.

---

 

Problem: Copying the text in a cell to another cell copies all the formatting of that cell

In Spreadsheet Component, when selecting the text using the mouse, the HTML markups are also selected even though the markups are invisible to the user.

Solution: A workaround is to use ctrl+c and ctrl+v to copy and paste text without copying the format.

---

 

Problem: Cell height does not automatically adjust

In Spreadsheet Component, if you increase the font size in a cell, the whole word might not be visible.

Solution: You need to manually adjust the cell height.

---

 

Problem: In calculator preview mode cannot edit spreadsheet

In Spreadsheet Component, if you select calculator preview, you are not able to change any values.

Comments: The full calculator mode is expected to be enabled in a future release.

---

Limitations in Spreadsheet
If you copy data and then paste it into another cell more than once, you might lose formatting during the pasting operation.
If you have a cell with a particular date format (such as yyyy/mm/dd), and then copy and paste the contents of that cell to another cell, you might be unable to change the date format of the new cell.
The values used in the select function should be entered in double quotes. For example, =select(3,"apple","baker","charlie","david")
Double-byte Character Sets are not supported when converting Lotus123 files into Spreadsheet Component files.
After converting a Spreadsheet Editor file to a Microsoft Excel file, hyperlinks are lost.
After converting a Spreadsheet Editor file to a Lotus123 file, the following can occur: background color is not reflected correctly currency formats are lost some cell borders change unicode characters are missing in the HTML view all colors are not converted the date value function gives the wrong value the round and ceiling functions give the wrong value some date formats are changed contents in a table are missing in the HTML view

---

Limitations for Locales in Spreadsheet
The Japanese era is not supported by Spreadsheet Component. Therefore, dates are not converted and are shown in the default format of mm/dd/yyyy.
In Norwegian, after converting a Microsoft Excel file to a Spreadsheet Editor file, functions such as text, financial, math, logic, and lookup) are lost.
In some locales, the first page of the Help Center displays but you cannot access any other page.
Some of the Spreadsheet Component helps for the Korean locale might not display correctly.

---

 

Related to Internet Explorer

Limitations in Spreadsheet on Internet Explorer
Some of the currency symbols do not display. Instead, a small box displays.
When using Internet Explorer on Windows 2000, some country names in the currency format dialog are garbled in some locales.

Error creating new document! - resourceNotFound,