MDM DM seeks excel by making calls to a function " CLSIDFromProgID " ( http://msdn.microsoft.com/en-us/library/windows/desktop/ms688386%28v=vs.85%29.aspx ) to look through the registry of the CLSID matching program progID .
In short, that makes MDM DM ? It seeks progID as :
- First " Excel.application.12 "
- Then " Excel.application.11 "
- Then " Excel.application.10 "
- Then " Excel.application.9 "
- Then " Excel.Application.8 "
Here are correpondances :
Microsoft Office Excel 2003
C: \ Program Files \ Microsoft Office \ Office11
Microsoft Excel 2002
C: \ Program Files \ Microsoft Office \ Office10
Microsoft Excel 2000
C: \ Program Files \ Microsoft Office \ Office
Microsoft Office Excel 2007
C: \ Program Files \ Microsoft Office \ Office12
Microsoft Office Excel 2010
C: \ Program Files \ Microsoft Office \ Office14
SAP would have been smarter to manage the key independent version, but no they have not done so MDM DM does not know anything beyond 2007 .
By adding key registers 11 in addition to those in 14 (there are not many ) export to Excel 2010 becomes functional .
