Graham Perrin's Library tagged Excel → View Popular

Filter:
All
Annotated

28 Jul 09

Doug Mahugh : Standards-Based Interoperability

blogs.msdn.com/...ds-based-interoperability.aspx - Preview

interop standard ODF Excel spreadsheet OpenFormula 2009 Office Open XML

Diagrams here are eye-catching. - grahamperrin on 2009-07-28

Standards-Based Interoperability
05 June 09
47 more annotations...
- Interoperability without Standards
- First, let’s consider how software interoperability works when it is not standards-based.
  
  Consider the various ways that four applications can share data, as shown in the diagram to the right. There are six connections between these four applications, and each connection can be traversed in either direction, so there are 12 total types of interoperability involved.
- As the number of applications increases, this complexity grows rapidly. Double the number of applications to 8 total, and there will be 56 types of interoperability between them:
- All complex software has bugs, and some bugs can present significant challenges to interoperability. Let’s consider the case that 3 of the 4 applications have bugs that affect interoperability, as shown in the diagram to the right.
- Here’s where those workarounds will need to be implemented:
  
  Note the complexity of this diagram.
- In the real world, interoperability is almost never achieved in this way. Standards-based interoperability is much better approach for everyone involved,
- whether that standard is an open one such as ODF (IS26300)
- or Open XML (IS29500)
- or a de-facto standard set by one popular implementation.
- each application implements the published standard as written, and this provides a baseline for delivering interoperability.
- The core premise of open standards-based interoperability is this:
- the existence of a standard addresses many of the issues involved, and the other issues can be addressed
- through standards maintenance, transparency of implementation details, and collaborative interoperability testing.
  - Issues relating to CalDAV are well addressed in these ways. - on 2009-07-28
  Add Sticky Note
- In the standards-based scenario, the standard itself is the central mechanism for enabling interoperability between implementations:
  
  This diagram is much simpler
- How this all applies to Office 2007 SP2
  
  I covered last summer the set of guiding principles that we used to guide the work we did to support ODF in Office 2007 SP2.
- applied in a specific order
- I’d like to revisit the top two guiding principles
- Guiding Principle #1: Adhere to the ODF 1.1 Standard
- Guiding Principle #2: Be Predictable
- Being predictable is also known as the principle of least astonishment.
- What about Bugs and Deviations?
  
  Of course, the existence of a published standard doesn’t prevent interoperability bugs from occurring.
- deviations from the requirements
- different interpretations
- Our approach to the transparency issue has been to document the details of our implementation through published implementer notes.
- Interoperability Testing
  
  The final piece of the puzzle is hands-on testing
- What else would you like to know about how Office approaches document format interoperability?
- a standard (evolved and improved as reality demands) is the proper foundation for resolving interoperabilty
- there is no question that users of other products are massively surprised by
- (1) their spreadsheets having their formulas lost when interchanged with Excel 2007
- (2) not being able to handle the formulase received in Excel 2007's ODF output.
- I am creating my own fantasy about the state of affairs
  - :-) - on 2009-07-28
  Add Sticky Note
- it is far too early to declare it to be unsuccessful
- I cannot fault the Microsoft approach as incorrect
- I was at the year-ago DII meeting where the guiding principles were announced and their application to spreadsheet formulas described. I applauded the principles and understood the reasoning for formulas.
- How this would impact various groups of users and non-users (who still want to interoperate) of Office 2007 did not surface in my consciousness.
- there is NO published standard for ODF spreadsheet formulas yet.
- Nor is there any de-facto standard that everyone agrees on.
- the “spaghetti diagram" method, with all of the complexity and risk of bugs that entails
- No implementer we know of has attempted that
- In the case of spreadsheet formulas, help is on the way -- OpenFormula is under development for use with ODF 1.2.
- I’d like to keep this thread on-topic
- I appreciate the post, very good
- Visually I would rather frame it in terms of convergence, a spiral.
- and user satisfaction.
- I doubt someone would ever find a magic bullet to interoperability
- New Comments to this post are disabled
  - Hurrah! - on 2009-07-28
  Add Sticky Note
- © 2009 Microsoft Corporation

Docstoc.com — free legal forms and business templates

www.docstoc.com/index.aspx - Preview

open library document share Microsoft Word Excel PowerPoint unread 2009

Referred from http://www.diigo.com/profile/infomancy - grahamperrin on 2009-07-28

21 Nov 06

Office 2004: Updates

www.macintouch.com/...topic2736.html - Preview

excel problem save vba 2006

An explanation and workaround for the "Document not saved" error that may occur within Excel.
- grahamperrin on 2006-11-20
[sussex.ac.uk #6611] - grahamperrin on 2006-11-21

Concerning my earlier message about Excel 2004 returning a "Document not saved" error on a workbook with VBA macros.
>

Turns out this is a common problem. On the mac it goes back to the 9.x days and covers all versions of Excel since then. Similar problems happen on windows machines. from http://www.microsoft.com/mac/community/community.aspx?pid=newsgroups (search on "document not saved" and/or "corrupt vba"), it's a 'known' problem with the VBA files collecting garbage.
>

VBA Code Cleaner

www.appspro.com/...CodeCleaner.htm - Preview

excel problem vba 2006

A workaround for the "Document not saved" error that may occur within Excel.
- grahamperrin on 2006-11-20
[sussex.ac.uk #6611] - grahamperrin on 2006-11-21

During the process of creating VBA programs a lot of
junk code builds up in your files. If you don't clean your files periodically you will begin to experience strange problems caused by this extra baggage. Cleaning a project involves exporting the contents of all its VBComponents to text files, deleting the
components and then importing the components back from the text files.

Combatting Template Bloat

word.mvps.org/...TemplateBloat.htm - Preview

excel fix problem vba word 2006

A Microsoft Most Valued Professional describes a fix for mysterious problems with Word and Excel.
- grahamperrin on 2006-11-20
[sussex.ac.uk #6611]
- grahamperrin on 2006-11-21

Why Word doesn't clean up after itself when saving a template which contains
a VBA project is one of the great mysteries of life. Excel suffers from the
same problem.