Known issues

This page contains a list of the known issues when using WrapCreator to convert Excel spreadsheets to live, calculating web pages.

Warning messages from Internet security programs

All our files and computers are scanned for malware at all stages of production using the latest versions of industry-standard Internet security software which is updated automatically. All files available from our Download page are free of known malware. If your Internet Security software is flagging any part of our software as malicious, we urge you to contact us immediately. We are aware that e2o2.exe or ViewManager.exe sometimes get a “suspected” status, but so far these have all been false alarms. Read more about Internet security.

Excel copies properties to new rows

When you insert a new row in Excel, the default behavior is that certain properties are copied from the row above it.

In the example below, we are inserting a new row below row 23.

Screenshot of a spreadsheet. The user is inserting a new row below a row with widgets.

After we have inserted a new row 24, can see in A24 that the Bold font style attribute was copied from A23.

Screenshot of a new row where the bold attribute was copied to a new row below.

If we insert a new row below a dropdown menu, cell B24 below the dropdown in A24 also becomes a dropdown menu, as you can see from the small handle.

Screenshot of a new row where a cell becomes a dropdown like the cell above it.

C24, the cell below the checkbox in C23, apparently did not become a checkbox. But something else happened to it, that is not easily recognized. Since C23 was unlocked, C24 quietly inherited the Unlocked attribute, which makes it an input cell.

Screenshot of a cell that becomes unlocked because the cell above is unlocked.

Conclusion: Whenever you insert a new row in an Excel spreadsheet, some cell attributes will be copied from the cells in the row above the inserted row. You can try to avoid this by always selecting a row below an apparently empty row, but you may still run into issues because many “invisible” cell attributes like Bold and Unlocked remain even after the cell’s contents are deleted, and will be inherited by the new row without any visual feedback.

This is how Excel is designed, and there is nothing that WrapCreator can do about it.

Task pane issues with Windows 10.1903

Windows 10 version 1903 introduced an error that caused the Excel task pane to stop working. The most apparent issue is that you cannot type anything into text fields in the task pane.

We have developed a circumvention for this problem. If you are affected by this error in Windows you should update to SpreadsheetConverter version 10.3 or later, or use a different version of Windows that doesn’t have the error.

Problems with multiple displays

As Excel develops, new features are added that may be incompatible with old display drivers. This may result in apparent formatting errors.

In some systems, you may get a truncated display where some parts of the window are obviously missing or incomplete. The solution is to use the Optimize for compatibility setting described below.


Screenshot of the licensing dialog with display issues

Issues related to high-resolution displays

Many modern tablets and laptops have displays with much higher resolution than their predecessors. Some people refer to this as having “a high dots-per-inch ratio”, or just “high DPI”. Excel gradually gets support for such “retina” screens, but you may still see scaling issues for add-ins like WrapCreator, especially when Excel is used with two or more monitors having different resolutions.

With some versions of Excel, you may find that the task pane contains large empty areas. Try maximizing the window, or reducing it to a non-maximized size.

Screenshot of the task pane with large empty areas

In some Excel versions, the text in the task pane may appear to be magnified and not proportional to the rest of the content on the screen.

Screenshot of the task pane when it is magnified due to DPI issues

Other symptoms of these scaling issues are:

  • When you click on WrapCreator buttons, menus or dropdown lists, the clickable area is very small, and the button or menu may appear not to work properly.

Use the setting “Optimize for compatibility”

There is a simple circumvention for these problems. In Excel, go to File > Options > General > User interface options and select Optimize for compatibility.

Screenshot of the high DPI setting for multiple displays

When using the Optimize for compatibility setting, Excel gets better at handling multiple screens with different resolutions. As you can see in the screenshot below, the WrapCreator task pane is now proportional to the rest of the screen.

Screenshot of a normal task pane in WrapCrator

Excel does not permit add-ins like WrapCreator to control the display scaling themselves. If your version of Excel doesn’t provide the compatibility mode for multiple displays, it will not properly support multiple displays with different resolutions, and you may see scaling issues like the ones described above until you upgrade Excel.

Cells that may contain both text and numbers

When we designed WrapCreator we wanted to allow for extremely large spreadsheets, and still provide exceptionally fast response times on slow hardware. This forced us into a few minor compromises, of which one was that if you ever assign a text value to a cell, it is always treated like text. When you reference such a cell in your spreadsheet, it always returns a text string, even if this string only contains numbers.

  • The cell contents will always be left-aligned, also when the string only contains numbers.
  • In string comparisons, the operation compares the two strings character for character from left to right, so string values containing numbers may give unexpected results, e.g. ‘9’ > ‘10’ and ‘09’ < ‘9’.
  • If you perform numeric operations with string values, the results may be unpredictable.

In spreadsheets that you intend to use with SpreadsheetConverter, you should clearly separate numeric variables from all other variables and never assign them any value that is not numeric.

Bad example: a formula that returns either text or a number

=IF($E2=0, "Error", ROUND(0.8/$H2,2))

WrapCreator will see that the formula may return the text Error and internally defines the cell as text, introducing the problems described above. To avoid this from happening, divide the functionality into two cells, one with the numeric value


And another with the error indication

=IF($E2=0, "Error", "")

Bad example: A formula that tests if a numeric cell is empty When you want to test if a numeric cell has no value, the correct way is to use a formula like

=IF(A1=0,"Empty", A1)

If you haven’t assigned any value to A1 yet, the formula above will fail, because WrapCreator regards empty cells as text strings, i.e. A1=””, and so the test will fail because A1<>0.

The obvious circumventions are:

  • Never use empty numeric cells – always initialize all numeric cells with a default value of 0.
  • Never use formulas that may assign text strings to numeric cells.

If you really, really must have a cell that contains both text and numbers, a safe test for it being empty is

=IF(OR(TRIM(A1)="", A1=0), "Empty", A1)

Use appropriate formulas

A common problem in Excel is that it may not show you the true, entire numeric value of a cell. For example, if you enter the formula


into cell A6, it will typically display as 0.333333. But the value actually has an infinite number of threes. So the statement

=IF(A6=0.333333, True, False)

will evaluate as False. Also, most computers actually perform decimal calculations as their equivalent binary calculations. This inherent approximation may lead to differences in precision, e.g. that a cell ends up with a value of 0.45000001 when you were expecting it to contain exactly 0.45. So, instead of the formula above, you should consider using

=IF(ABS(A6-0.333333) < 0.000001, True, False)

The same thing happens if you want to evaluate if a value is less than or greater than another value. If you get unexpected True situations using

=IF(A5 > A6, True, False)

it may be because one of the cells contains 0.45 but the other 0.45000001. To exclude this special case – where you prefer to consider the cells to be equal – use this formula instead:

=IF(AND(ABS(A5-A6) > 0.000001, A5 > A6), True, False)

If the numbers are close enough, the first part of the AND statement will not be True, and so A5 will not be considered greater than A6. You must use a “proximity constant” that is relevant for the numbers you are actually processing, in particular if you expect the cells to contain extremely high or low values.

Dynamic arrays

Excel versions that support dynamic arrays allow a function to return multiple values, where formula results to spill over to adjacent cells. WrapCreator currently only supports functions that return a single value and does not support dynamic arrays. Unfortunately, there is no way to tell Excel that all our own functions only return single values.

Older versions of Excel silently ignored all but one value in an array result, a feature referred to as an implicit intersection. To provide compatibility, Excel versions that do support dynamic arrays automatically add the implicit intersection operator @ to some formulas created with earlier versions of Excel – including the entire set of functions used by WrapCreator.


This is correct and the formulas continue to calculate the same way they always have. If you edit the formula, you may be invited to read the Help text for implicit intersection with this prompt:

Screenshot of a warning message in Excel regarding the implicit intersection operator @

You should not remove any @ operators added to your formulas. They simply mean that implicit intersection is applied, like it always was before. If you remove an automatically added @ from a formula, you explicitly make it an array formula. If you later open the same workbook in an older version of Excel, the formula will appear as a legacy array formula wrapped with braces {}. This is done to prevent the older version from applying implicit intersection.


Threaded comments are unsupported

This issue requires you to know what version of Excel you are using. This information is available on the File > Account screen. Screenshot of the File > Account screen in Excel In Excel 365, version 1810, Microsoft introduced Threaded Comments. The new feature also became available in Excel 2016 version 16.17. With threaded comments, you can discuss a value or formula with other users of the same spreadsheet, just like in a chat or e-mail conversation. Notice the Reply… field in the screenshot below.

The old comments are now referred to as Notes. Notes look and work just like Comments have worked before.

WrapCreator supports Comments from previous versions of Excel, and Notes from Excel version 1810 or 16.17, or later. If you use threaded comments in a spreadsheet that you convert with WrapCreator, the threaded comments will not be visible in the converted web page.

Restrictions for spreadsheet file name, size and content

For your spreadsheet to convert gracefully into a properly formatted web page, it must follow certain rules. We have documented these in a separate help page about the restrictions for spreadsheet file name, size and content.

A conversion run never finishes

If you start a conversion and the progress bar seems to get stuck around 32%, you may be using conditional formatting on a very large cell range, e.g. an entire column. This problem is easily solved, just apply conditional formatting to only those cells that actually contain data.

Empty sheets are not visible on the web page

When you convert a spreadsheet where one or more of the worksheets are empty, the empty worksheets will not appear in the converted web page.

An error message appears instead of Google Maps

New Google Maps may not appear as expected on your website. You get an error message saying Oops! Something went wrong. You likely have a problem with the Google Maps API key you use to show maps.

Screenshot of the error mesage you get for a Google Map without an API key