PowerPivot for Excel is a data analysis tool that delivers unmatched computational power directly within the application users already know and love—Microsoft Excel. Office 2010 is the next version of Office 2010. We all know Office 2010 is on the verge of getting released and the reviews available online say that it’s a phenomenal product.
Let us read the piece he sent for SQLAuthority.com readers to aid them with Office 2010 Readiness Check
Are you ready for Office 2010? It may look simple for an end-user, but when you look it from an enterprise perspective, there are lots of things which need to be considered before the migration and Compatibility stands out to be one big stop point. Compatibility issues may cover everything right from your environment till the addins which you develop.
Microsoft has released 2 tools (Office Environment scanning tool (OEAT) and Compatibility Inspector) which will exactly help you address this concern.
Office Environment scanning tool (OEAT)
This a comprehensive tool which (along with documentation) assists a customer in the assessment phase of deployment. It identifies the currently installed applications and installation environment, add-ins currently in use by Office clients, programs that are not registered as add-ins but still interact with Office programs, provides a report on the Environmental assessment (potential upgrade issues) and also reports the Add-ins assessment–list of third party programs and information about the compatibility of those programs with Microsoft Office 2010.
Read this article to know more on how you can use the Office Environment scanning tool (OEAT)
Microsoft Office 2010 Compatibility Inspector
This tool compares existing code against the Office 2010 object model by using a text search for known properties and methods that have changed. It includes a basic scanner where definitions and remediation links are updated from a central online location. It also generates a summary report and a details report. The summary includes the total lines of code scanned as well as total lines identified as potential candidates for object model changes. The details report includes the module name, line number, and links to remediation for each identified issue along with color-coded flags for impact guidance. You can run the tool against specific projects. This tool is available as an addins for both Office and Visual Studio.
Read this article to know more on how you can use the Compatibility Inspector (http://www.msigeek.com/2821/fixing-code-compatibility-issues-with-office-2010-compatibility-inspector)
Reference: Pinal Dave (https://blog.sqlauthority.com)