Graham,

This issue has been submitted to our development team for further review.  The reference number for this item is 118188.  A support case has also been opened for you.  The number for the support case is CAS-97068-FSD2VG.  I will leave this case open and update you with any new information after the review.  You can also continue to send updates to this case at any time.  Please let me know if you need more information.

Thanks very much for your help.

I have done a bit of further digging and discovered:

a. If I use a spreadsheet actually created in Excel 97-2003 (rather than 2007 and saved in 97-2003 format) AND do not write any data, then when I open the spreadsheet after calling oWorkbook.Save() I do not get an error message from Office but the graph has lost its mapping to the cells.

b. If I use the Excel 97-2003 spreadsheet above and just make a single write with:

oWorkSheet.GetCell( "C21" ).Value = 10

The spreadsheet goes crazy! Formatting has changed on all cells in the range mapped to the chart, rotated text has changed back to horizontal. Have a look at Row 1 and row 20.

Thanks for your help

Thanks for providing the file. I am getting the same results here with the latest code. Looks like the issue still exists. I have forwarded this post to the Developer Support Manager and a DS engineer will be contacting you about this issue.

Hi Mike

I have installed 12.1 and rebuilt the application and I still get the same problem.

I have attached the spreadhseet. The worksheet I am using is called "KPI PPM 3 - High Risk"

Thanks

Well I wasn't suggesting you update to 12.1 just yet. I just want to know if this issue has been addressed yet, but I will answer your questions anyway:

1. Yes the 12.1 Excel library can run with VS 2005
2. It depends. If you want to run the 10.2 and 12.1 Excel libraries side-by-side, then no, you will have naming conflicts unless you alias one of the assemblies. Also, if you are using one of our grid excel exporter assemblies in your application, the answer is also no because the 10.2 grid exporter assembly needs to reference the 10.2 Excel assembly. However, if you are just using the Excel assembly by itself, you can use the 12.1 version of that and the 10.2 version of our other controls and there shouldn't be a problem.
3. It would be possible to downgrade if you don't start using any of the newer features introduced after 10.2.
4. Yes, 12.1 still supports CLR2.

To attach the Excel sheet, reply to the post, click on the Options tab and click "Add/Update".