Quantcast
Channel: NPOI
Viewing all 1621 articles
Browse latest View live

Commented Unassigned: cannot choose sheet protect options [13643]

$
0
0
Sheet.LockXXXX methods changes internal lock state to 'true' (=locked)
but there's no way to change state 'false'.
・default protection property is almost 'true'
・ProtectSheet method creates new protection object (with default property value=true=locked)
so we cannot choose protect options. all operations are locked.

I tried to change internal state via reflection
and I got desired results.

and I found HSSFSheet LockFormatCells changes wrong field

My suggestion:
a. add UnLockXXXXMethod
b. change default lock state false. and use LockXXXX methods
c. add access method to CT_Worksheet
Comments: ** Comment from web user: raavishpatel **

Hi,

I have also facing same issue with me.

So can you please tell me how you are using __change internal state via reflection__ method for got your desired result.

Thanks


Commented Unassigned: 2007 format Excel file corrupted [13809]

$
0
0
We use NPOI to modify an existing template and save it as a new one.
The new Excel file created by NOPI is always corrupted. When the file is opened, it says' We found a problem with some content in 'FileName.xlsx'.Do you want us to try to recover as much as we can? If you trust the source of this workbook, Click Yes" (发现FileName.xlsx 中部分内容有问题。是否让我们尽量尝试恢复?如果您信任次工作簿的源,请单击是)
We narrow down the condition, just use NPOI to open it and then save as a new file. The file will be corrupted.
We try the newest version 2.2.0, but in vain.
Comments: ** Comment from web user: xbrabec **

Same problem here

New Post: how to remove sheet name on conversion to html

$
0
0
hi, i'm using this code to convert xls to html. in the html i don't want the sheet name , is there a way to exclude from conversion?

HSSFWorkbook workbook = ExcelToHtmlUtils.LoadXls(fileSource);
ExcelToHtmlConverter excelToHtmlConverter = new ExcelToHtmlConverter();
excelToHtmlConverter.OutputColumnHeaders = true;
excelToHtmlConverter.OutputHiddenColumns = false;
excelToHtmlConverter.OutputHiddenRows = false;
excelToHtmlConverter.OutputLeadingSpacesAsNonBreaking = true;
excelToHtmlConverter.OutputRowNumbers = false;
excelToHtmlConverter.UseDivsToSpan = false;
excelToHtmlConverter.ProcessWorkbook(workbook);
excelToHtmlConverter.Document.Save(fileTarget);

Created Unassigned: NPOi导出2007版的时候 ,数据一多久打不开了 [13876]

$
0
0
导出几百行文件正常打开,导出3万多行就打不开了,提示文件损坏!

Commented Unassigned: NPOi导出2007版的时候 ,数据一多就打不开了 [13876]

$
0
0
导出几百行文件正常打开,导出3万多行就打不开了,提示文件损坏!
Comments: ** Comment from web user: tonyqus **

WPS is not supported by NPOI. Please let me know if the file works on Microsoft Office.

Updated Release: NPOI 2.2.1

$
0
0
Bug Fixes
- Fix weird XSSF CellStyle Border behaviour
- Fix a lot of serialization issue of ooxml issue
- Fix phonetic guides tag reading/writing issue
- Fix XWPFRun SetText exception issue
- Fix xml security issue
- Optimize AutoResizeColumn for memory
- Fix sqref property is missing on ProtectedRange
- Fix drawing ooxml issue and cell value bug
- Fix numFmtId property issue on NumFmt node
- Fix ooxml issues for RadarChart and CellStyle
- Fix xfrm namespace issue in ooxml
- Fix ScatterChart issue in ooxml
- Fix ooxml bugs in Vml entities

Commented Issue: RemoveRow doesn't work as expected [3493]

$
0
0
When I use the RemoveRow function everything looks like it has worked, but the exported excel 2003 file still contains the row. If I do not open the excel file and try to rerun the query then I get the following error "Unexpected missing row when some rows alReady present" If I open the file and then close it the file size changes and I can run the RemoveRow function again without the error. I have office 2007 installed on my computer if that makes a difference.
Comments: ** Comment from web user: paradise80 **

however, I can still reproduce this bug in 2.1.3.1 for XLSX file...

Created Unassigned: ISheet.RemoveRow does not work correctly [13887]

$
0
0
v2.1.3.1 XLSX format

1. use RemoveRow to remove the 2nd row
2. create a new row as the 2nd row and set cells value.
3. Write to file.

When I open the save file, the first row was remove and blank, and the 2nd row also blank.

Also see my question on SO:
http://stackoverflow.com/questions/36515060/npoi-not-write-all-cells-out

New Post: Saving large workbooks

$
0
0
I'm having a similar problem but on the reading side with large XSSF (*.xlsx) workbooks.

This runs out of memory on a 50 megabyte excel file I'm trying to read (uses over 1.7 gigs before running out of memory):
        FileStream fs = new FileStream("foo.xlsx", FileMode.Open);
        NPOI.SS.UserModel.IWorkbook wb = new NPOI.XSSF.UserModel.XSSFWorkbook(fs);
Note: this same file opens in Excel with only 150 megs of memory getting used.

PS - I'm also unable to find the XSSF package when I browse the on-line web interface for SOURCE code. Am I looking in the wrong online codebase?

Commented Unassigned: Exporting large files into XLSX [13605]

$
0
0
Hi,

I have a requirement where I need to create and excel file with 15000 records and 300 columns.
When I try to save the file using the following code

using (var fileData = new System.IO.FileStream(fileName, System.IO.FileMode.Create))
{
workbook.Write(fileData);
}
it is failing with OutOfMemoryException.

My question is how can I save large files (>30MB).

Thanks
Vijay
Comments: ** Comment from web user: ebyrob **

In Apache POI there is a serialized version of at least the XSSF side of things.

org.apache.poi.xssf.streaming.SXSSFWorkbook

I don't see this implemented in NPOI currently, but I'm hoping sometime in the future this can be ported over to C#.

Note: I'm having the same problem you are, but with reading a large XLSX file:

FileStream fs = new FileStream("foo.xlsx", FileMode.Open);
NPOI.SS.UserModel.IWorkbook wb = new NPOI.XSSF.UserModel.XSSFWorkbook(fs);

OutOfMemoryException (on 50 meg file using 1.7 gigs in process) at XSSFWorkbook constructor.

Updated Wiki: Home

$
0
0
Who are We
Neuzilla is the studio behind NPOI. For detail, you can check http://blog.neuzilla.com/.
公众号badge
 
What's NPOI
This project is the .NET version of POI Java project at http://poi.apache.org/. POI is an open source project which can help you read/write xls, doc, ppt files. It has a wide application.
 
Our Sponsor (赞助商)
 
E-iceblue is a community sponsor of NPOI. 提供中文技术支持
Don't forget to have a try on Free Spire.XLS
XLS
 
 
What NPOI can do
For example, you can use it to
a. generate a Excel report without Microsoft Office suite installed on your server and more efficient than call Microsoft Excel ActiveX at background;
b. extract text from Office documents to help you implement full-text indexing feature (most of time this feature is used to create search engines).
c. extract images from Office documents
d. generate Excel sheets that contains formulas
 
Donate NPOI

支付宝捐款账号: tonyqus@163.com
Paypal: tonyqus@gmail.com


donate_btn
 
 
Advantage of NPOI
a. It's totally free to use
b. Cover most features of Excel (cell style, data format, formula and so on)
c. Support xls, xlsx, docx.
d. Designed to be interface-oriented (take a look at NPOI.SS namespace)
e. Support not only export but also import
f. .Net 2.0 based even for xlsx and docx (though we also support .NET 4.0)
g. Successful cases from all over the world
h. huge amout of basic examples
i. No dependency on isolated storage
 
To get the latest code, please visithttps://github.com/tonyqus/npoi.
 
 
Comments from NPOI users
image
image
image
image
image
 
 
Tutorial

NPOI on SNS
中文
QQ群: 189925337
 
English

System Requirement
VS2010 with .NET 4.0 runtime
VS2005 or VS2008 with .NET 2.0 Runtime (SP1)
vs2003 with .NET 1.1
Mono
medium trust environment in ASP.NET

 

 

 
Extensions
 

Updated Wiki: Home

$
0
0
Who are We
Neuzilla is the studio behind NPOI. For detail, you can check http://blog.neuzilla.com/.
公众号badge
 
What's NPOI
This project is the .NET version of POI Java project at http://poi.apache.org/. POI is an open source project which can help you read/write xls, doc, ppt files. It has a wide application.
 
Our Sponsor (赞助商)
 
E-iceblue is a community sponsor of NPOI. 提供中文技术支持
Don't forget to have a try on Free Spire.XLS
XLS
 
 
What NPOI can do
For example, you can use it to
a. generate a Excel report without Microsoft Office suite installed on your server and more efficient than call Microsoft Excel ActiveX at background;
b. extract text from Office documents to help you implement full-text indexing feature (most of time this feature is used to create search engines).
c. extract images from Office documents
d. generate Excel sheets that contains formulas
 
Donate NPOI

支付宝捐款账号: tonyqus@163.com
Paypal: tonyqus@gmail.com


donate_btn
 
 
Advantage of NPOI
a. It's totally free to use
b. Cover most features of Excel (cell style, data format, formula and so on)
c. Support xls, xlsx, docx.
d. Designed to be interface-oriented (take a look at NPOI.SS namespace)
e. Support not only export but also import
f. .Net 2.0 based even for xlsx and docx (though we also support .NET 4.0)
g. Successful cases from all over the world
h. huge amout of basic examples
i. No dependency on isolated storage
 
To get the latest code, please visithttps://github.com/tonyqus/npoi.
 
 
Comments from NPOI users
image
image
image
image
image
 
 
Tutorial

NPOI on SNS
中文
QQ群: 189925337
 
English

System Requirement
VS2010 with .NET 4.0 runtime
VS2005 or VS2008 with .NET 2.0 Runtime (SP1)
vs2003 with .NET 1.1
Mono
medium trust environment in ASP.NET

 

 

 
Extensions
 

Updated Wiki: Home

$
0
0
Who are We
Neuzilla is the studio behind NPOI. For detail, you can check http://blog.neuzilla.com/.
公众号badge 
What's NPOI
This project is the .NET version of POI Java project at http://poi.apache.org/. POI is an open source project which can help you read/write xls, doc, ppt files. It has a wide application.
 
Our Sponsor (赞助商)
 
E-iceblue is a community sponsor of NPOI. 提供中文技术支持
Don't forget to have a try on Free Spire.XLS
XLS
 
 
What NPOI can do
For example, you can use it to
a. generate a Excel report without Microsoft Office suite installed on your server and more efficient than call Microsoft Excel ActiveX at background;
b. extract text from Office documents to help you implement full-text indexing feature (most of time this feature is used to create search engines).
c. extract images from Office documents
d. generate Excel sheets that contains formulas
 
Donate NPOI

支付宝捐款账号: tonyqus@163.com
Paypal: tonyqus@gmail.com


donate_btn
 
 
Advantage of NPOI
a. It's totally free to use
b. Cover most features of Excel (cell style, data format, formula and so on)
c. Support xls, xlsx, docx.
d. Designed to be interface-oriented (take a look at NPOI.SS namespace)
e. Support not only export but also import
f. .Net 2.0 based even for xlsx and docx (though we also support .NET 4.0)
g. Successful cases from all over the world
h. huge amout of basic examples
i. No dependency on isolated storage
 
To get the latest code, please visithttps://github.com/tonyqus/npoi.
 
 
Comments from NPOI users
image
image
image
image
image
 
 
Tutorial

NPOI on SNS
中文
QQ群: 189925337
 
English

System Requirement
VS2010 with .NET 4.0 runtime
VS2005 or VS2008 with .NET 2.0 Runtime (SP1)
vs2003 with .NET 1.1
Mono
medium trust environment in ASP.NET

 

 

 
Extensions
 

Updated Wiki: Home

$
0
0
Who are We
Neuzilla is the studio behind NPOI. For detail, you can check http://blog.neuzilla.com/.
公众号badge 
What's NPOI
This project is the .NET version of POI Java project at http://poi.apache.org/. POI is an open source project which can help you read/write xls, doc, ppt files. It has a wide application.
 
For example, you can use it to
a. generate a Excel report without Microsoft Office suite installed on your server and more efficient than call Microsoft Excel ActiveX at background;
b. extract text from Office documents to help you implement full-text indexing feature (most of time this feature is used to create search engines).
c. extract images from Office documents
d. generate Excel sheets that contains formulas
 
Our Sponsor (赞助商)
 
E-iceblue is a community sponsor of NPOI. 提供中文技术支持
Don't forget to have a try on Free Spire.XLS
XLS
 
 
Donate NPOI

支付宝捐款账号: tonyqus@163.com
Paypal: tonyqus@gmail.com


donate_btn
 
 
Advantage of NPOI
a. It's totally free to use
b. Cover most features of Excel (cell style, data format, formula and so on)
c. Support xls, xlsx, docx.
d. Designed to be interface-oriented (take a look at NPOI.SS namespace)
e. Support not only export but also import
f. .Net 2.0 based even for xlsx and docx (though we also support .NET 4.0)
g. Successful cases from all over the world
h. huge amout of basic examples
i. No dependency on isolated storage
 
To get the latest code, please visithttps://github.com/tonyqus/npoi.
 
 
Comments from NPOI users
image
image
image
image
image
 
 
Tutorial

NPOI on SNS
中文
QQ群: 189925337
 
English

System Requirement
VS2010 with .NET 4.0 runtime
VS2005 or VS2008 with .NET 2.0 Runtime (SP1)
vs2003 with .NET 1.1
Mono
medium trust environment in ASP.NET

 

 

 
Extensions
 

Released: NPOI 2.2.0 (Aug 01, 2015)

$
0
0
This is pre-release version of NPOI 2.2.0.

NOTE: There is no corresponding nuget release for alpha version.

New Feature
1. Implement FIXED, PROPER, DMIN and DGET functions
2. XSSF support for evaluating formula references to other Workbooks
3. Read text from SDTs at the table cell level, including (sometimes) Cover Page, Table of Contents and Bibliography
4. Double Strikethrough support for XWPF runs
5. XSSFSheet support for getDrawingPatriarch(), alongside the existing createDrawingPatriarch() method
6. Start on common interfaces for Paragraphs and Character Runs for XWPF
7. Basic text extractor for older Excel 4,5 and 95 formats
8. Add NPOIFS in-place write support, including updating the contents of existing entries
9. Support loading .xlsx files with no Styles Table

POI Bug fixes
57880 - Handle >32,767 cell styles and formats in XSSF (file format limit is 64,000)
57826 - If a XSSF shape has a buFont but no bullet character, mirror Excel and treat as un-bulleted
56017 - Fix shifting comments with shifted rows
56295 - Fix cloning of styles across workbooks and handling of default value of attribute applyFill
56380 - Remove limitation of 1024 comments per Workbook
56467 - Fix cloning of sheets with pictures
57171 - Adjust the active sheet in setSheetOrder()
57163 - Adjust the active sheet in removeSheet()
57165 - Avoid PartAlreadyExistsException when removing/cloning sheets
57196 - Resolve RefEval to it's inner ValueEval in Hex2Dec
57482 - Handle XSLX files with no shared strings table in read-only mode
46898 - XSSF: Return #VALUE! for circular references.
46912 - Add methods to query outline level for HSSF and XSSF
49541 - Mapping of symbol characters to unicode equivalent
57007 - Add initial implementations of DMIN and DGET functions
57373 - Fix get/setFirstVisibleTab() for XSSFWorkbook
57231 - Add missing ArrayRecord.clone()
56511 - Fix NullPointerException for RichText strings with no formatting for some runs.
56888 - XSSFDataValidation ignores "allow blank" read from sheet, assumes true
57236 -
57254 - XWPF: Correctly build internal list of styles when styles are added
57312 - XWPF: Add check for null value of underline w:val
57355 -
57164 - XSSFDrawing.createCellComment() does not honor dx and dy values passed in
57003 - Add implementation of function FIXED
57185 - Correct naming from "Serie" to "Series"
57010 - Add implementation of function PROPER
55280 - XSSF: Greatly improve performance of shifting rows in sheets with many merged regions.
48195 - Formulas: Fix incorrect evaluation of IF() with ROW()/COLUMN() as else-result.
56914 - XSSFRowShifter.updateConditionalFormatting throws IOOBE when there are more than 1 CTConditionalFormatting
51222 - XSSFColor.getARGBHex() returns wrong color for Excel 2007 xlsx file
56864 - XWPFLatentStyles.isLatentStyle always returns true if there is at least 1 lsdException
57151 - And documentation and validation in CellRangeAddress to prevent invalid row/column combinations


Updated Release: NPOI 2.2.0 (八月 01, 2015)

$
0
0
This is pre-release version of NPOI 2.2.0.

NOTE: There is no corresponding nuget release for alpha version.

New Feature
1. Implement FIXED, PROPER, DMIN and DGET functions
2. XSSF support for evaluating formula references to other Workbooks
3. Read text from SDTs at the table cell level, including (sometimes) Cover Page, Table of Contents and Bibliography
4. Double Strikethrough support for XWPF runs
5. XSSFSheet support for getDrawingPatriarch(), alongside the existing createDrawingPatriarch() method
6. Start on common interfaces for Paragraphs and Character Runs for XWPF
7. Basic text extractor for older Excel 4,5 and 95 formats
8. Add NPOIFS in-place write support, including updating the contents of existing entries
9. Support loading .xlsx files with no Styles Table

POI Bug fixes
57880 - Handle >32,767 cell styles and formats in XSSF (file format limit is 64,000)
57826 - If a XSSF shape has a buFont but no bullet character, mirror Excel and treat as un-bulleted
56017 - Fix shifting comments with shifted rows
56295 - Fix cloning of styles across workbooks and handling of default value of attribute applyFill
56380 - Remove limitation of 1024 comments per Workbook
56467 - Fix cloning of sheets with pictures
57171 - Adjust the active sheet in setSheetOrder()
57163 - Adjust the active sheet in removeSheet()
57165 - Avoid PartAlreadyExistsException when removing/cloning sheets
57196 - Resolve RefEval to it's inner ValueEval in Hex2Dec
57482 - Handle XSLX files with no shared strings table in read-only mode
46898 - XSSF: Return #VALUE! for circular references.
46912 - Add methods to query outline level for HSSF and XSSF
49541 - Mapping of symbol characters to unicode equivalent
57007 - Add initial implementations of DMIN and DGET functions
57373 - Fix get/setFirstVisibleTab() for XSSFWorkbook
57231 - Add missing ArrayRecord.clone()
56511 - Fix NullPointerException for RichText strings with no formatting for some runs.
56888 - XSSFDataValidation ignores "allow blank" read from sheet, assumes true
57236 -
57254 - XWPF: Correctly build internal list of styles when styles are added
57312 - XWPF: Add check for null value of underline w:val
57355 -
57164 - XSSFDrawing.createCellComment() does not honor dx and dy values passed in
57003 - Add implementation of function FIXED
57185 - Correct naming from "Serie" to "Series"
57010 - Add implementation of function PROPER
55280 - XSSF: Greatly improve performance of shifting rows in sheets with many merged regions.
48195 - Formulas: Fix incorrect evaluation of IF() with ROW()/COLUMN() as else-result.
56914 - XSSFRowShifter.updateConditionalFormatting throws IOOBE when there are more than 1 CTConditionalFormatting
51222 - XSSFColor.getARGBHex() returns wrong color for Excel 2007 xlsx file
56864 - XWPFLatentStyles.isLatentStyle always returns true if there is at least 1 lsdException
57151 - And documentation and validation in CellRangeAddress to prevent invalid row/column combinations

Released: NPOI 2.1.3.1 (Feb 22, 2015)

$
0
0
关注官方微信公众号, 请搜索"架构师联盟"

BUG FIXES
a. fix word serialization issues
b. fix CloneStyleFrom issue
c. Fix vertical alignment default value for XSSFCell
d. fix setAutoFilter change range issue
e. fix EDate function
f. fix FormatException in FormulaParser
g. fix Comment random Shape issue (comment serialization issue)
h. fix not be able to unlock the cell issue

POI BUG FIXES
55729 - DataFormatter should format Error cells, returning the Excel error string
49237 - HSSF Row Style XfIndex is 12 not 16 bits of data
54607 - NullPointerException in XSSFSheet.getTopRow() when the top row is 1
55745 - fix handling of tables in XSSF if there are comments as well
54673 - Simple wildcard support in HLOOKUP, VOOLKUP, MATCH, COUNTIF
55047 - REPT formula support
55042 - COMPLEX formula support
55041 - CODE formula support
54508 - EDATE formula support
53966 - IfError support (from Analysis Toolpak)
54402 - IfError handling of indirect references

NEW FEATURES
a. Add ReplaceText to XWPFParagraph and XWPFRun
b. adjust ExcelExtractor interface
c. Improving comment missing handling in HSSFSheet
d. copy hyperlink in CopySheet and fix some bugs
e. Implement ChartSheet in OpenXmlFormats
f. Implement shrinktofit for XSSF

Updated Release: NPOI 2.1.3.1 (二月 22, 2015)

$
0
0
关注官方微信公众号, 请搜索"架构师联盟"

BUG FIXES
a. fix word serialization issues
b. fix CloneStyleFrom issue
c. Fix vertical alignment default value for XSSFCell
d. fix setAutoFilter change range issue
e. fix EDate function
f. fix FormatException in FormulaParser
g. fix Comment random Shape issue (comment serialization issue)
h. fix not be able to unlock the cell issue

POI BUG FIXES
55729 - DataFormatter should format Error cells, returning the Excel error string
49237 - HSSF Row Style XfIndex is 12 not 16 bits of data
54607 - NullPointerException in XSSFSheet.getTopRow() when the top row is 1
55745 - fix handling of tables in XSSF if there are comments as well
54673 - Simple wildcard support in HLOOKUP, VOOLKUP, MATCH, COUNTIF
55047 - REPT formula support
55042 - COMPLEX formula support
55041 - CODE formula support
54508 - EDATE formula support
53966 - IfError support (from Analysis Toolpak)
54402 - IfError handling of indirect references

NEW FEATURES
a. Add ReplaceText to XWPFParagraph and XWPFRun
b. adjust ExcelExtractor interface
c. Improving comment missing handling in HSSFSheet
d. copy hyperlink in CopySheet and fix some bugs
e. Implement ChartSheet in OpenXmlFormats
f. Implement shrinktofit for XSSF

Updated Wiki: Home

$
0
0
Who are We
Neuzilla is the studio behind NPOI. For detail, you can check http://blog.neuzilla.com/.
公众号badge
 
What's NPOI
This project is the .NET version of POI Java project at http://poi.apache.org/. POI is an open source project which can help you read/write xls, doc, ppt files. It has a wide application.
 
For example, you can use it to
a. generate a Excel report without Microsoft Office suite installed on your server and more efficient than call Microsoft Excel ActiveX at background;
b. extract text from Office documents to help you implement full-text indexing feature (most of time this feature is used to create search engines).
c. extract images from Office documents
d. generate Excel sheets that contains formulas
 
Our Sponsor (赞助商)
 
E-iceblue is a community sponsor of NPOI. 提供中文技术支持
Don't forget to have a try on Free Spire.XLS
XLS
 
 
Donate NPOI

支付宝捐款账号: tonyqus@163.com
Paypal: tonyqus@gmail.com


donate_btn
 
 
Advantage of NPOI
a. It's totally free to use
b. Cover most features of Excel (cell style, data format, formula and so on)
c. Support xls, xlsx, docx.
d. Designed to be interface-oriented (take a look at NPOI.SS namespace)
e. Support not only export but also import
f. .Net 2.0 based even for xlsx and docx (though we also support .NET 4.0)
g. Successful cases from all over the world
h. huge amout of basic examples
i. No dependency on isolated storage
 
To get the latest code, please visithttps://github.com/tonyqus/npoi.
 
 
Comments from NPOI users
image
image
image
image
image
 
 
Tutorial

NPOI on SNS
中文
QQ群: 189925337
 
English

System Requirement
VS2010 with .NET 4.0 runtime
VS2005 or VS2008 with .NET 2.0 Runtime (SP1)
vs2003 with .NET 1.1
Mono
medium trust environment in ASP.NET

 

 

 
Extensions
 

Created Unassigned: corrupt XLSX file after reference (formlua) to a CellValue, which contains a "&" sign [13893]

$
0
0
I am using:

- Visual Studio 2012 Pro. Patch 5
- MS Office 2010 Ent. SP2 and last patches
- NPOI version 2.1.3.1 via NuGet

How to reproduce:

1. Create a XLSX file with Office 2010 with a CellValue("&") in maybe cell A1 on first sheet
2. Add a formula on the seconde sheet in A1 what is a reference of A1 on the first sheet
3. save the file

4. Open file with NPOI as IWorksheet don't edit it
5. save it

Result is a corrupt XLSX, what you cannot open with MS Excel.
If you repait it, i will remove the reference (formula) on the second sheet.

I can open a file with MS Office 2010, which does not contains a "&" sign without problems!
The file is corrupt if there is a reference to a value with a "&" sign, without reference and "&" ... no problem to open it.
Viewing all 1621 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>