Export (0) Print
Expand All

Analyze reports from OMPM

Updated: October 24, 2008

Applies To: Office Resource Kit

Updated: 2008-10-24

In this article:

You can use OMPM Reports to perform the following actions:

  • Review OMPM File Scanner results to identify errors or to view coverage by computer.

  • Manage issues.

  • Create a list of files to convert and export the list to a file for use by the Office File Converter (OFC) or the Version Extraction Tool (VET).

  • Review data compatibility issues between Access version 1997 or earlier and Access version 2000 or later.

Starting OMPM Reports

  1. In the Reports folder where you installed OMPM, double-click OMPM.accdr. Click Yes at the security prompt.

  2. If this is your first time using OMPM Reports, enter the location of an OMPM database to connect to.

  3. In the Server: drop-down box on the OMPM Welcome page, select the SQL or SQL Express server that you created earlier. If the server is not the default for a computer, it must be specified as the named instance in the form <ComputerName>\<ServerName>. By default, SQL Server installs itself as the default instance on a server, but SQL Express installs itself using SQLEXPRESS as the named instance.

  4. In the Database: drop-down box, select the name of the database. Click Connect. If you have already connected to a database, OMPM Reports automatically open the database. If you want to connect to a different database, click Connect.

    NoteNote:

    The SQL Server database can support millions of results. However, for easier manageability, you might want to have multiple smaller databases.

Review Scan Coverage and Errors

  1. On the OMPM Welcome page, select Scan Coverage and Errors. This brings up the Scan Results page.

  2. Select a Run ID at the top of the Scan Results page to view the results for that run of the OMPM File Scanner.

  3. To view the scan results for a specific computer, select the computer in Scan results for each computer in the run selected above. The scan results appear in Scan errors for the run and computer selected above.

NoteNote:

Only scanner coverage and errors are reported here. Use the Office 2007 Compatibility report for upgrade issues identified by the scanner.

The Severity Levels that help map to types of errors, which might occur, in bulk converting the file to the 2007 Office system format, from the table in the OMPM database are shown in the following table.

ColorIssue Level IDDescription

Red

1

Known issues that might cause significant data loss (for example, Word edit version loss) or might cause a conversion to fail.

Yellow

2

Will convert into the 2007 Office system format, but there might be some format or minor data loss issues.

Green

3

Light cosmetic issues, no data loss.

No Issue

4

No issues.

The following table provides a complete list of the errors the scanner can generate for Word, Excel, and PowerPoint, taken from the OMPM database.

Issue IDTitleDescriptionIssue Level IDIssue Type ID

1000

File Deleted

The file no longer exists at the requested location.

1

2

1001

File Access Error

The file location could not be accessed, probably because a computer was inaccessible.

2

2

1002

File Modified

The file modified date did not match the modified date in the file list.

1

2

1003

No Write Permissions

The user account does not have permissions to write to the file.

2

3

1010

Not Deep Scanned

The file has not been deep scanned yet.

2

4

1050

File Scan Error

An error occurred while scanning this file. Review the Scan Coverage and Errors report for more information.

2

3

1100

Document contains versions

Edited versions of the document will be removed on opening the file in Microsoft Office Word 2007, even in compatibility mode.

1

1

1200

Send for review data

This file has review comments and contains a hidden baseline copy of the original. Microsoft Office PowerPoint 2007 discards the hidden copy and saving removes it permanently. Users cannot tell which edits reviewers made if reopened in previous versions.

1

1

1201

Embedded documents

There are potential performance, security, and fidelity issues with embedded documents.

2

1

1202

VBA code

This file contains embedded VBA code. This can create security, fidelity, performance, and solution compatibility issues. Check this file for compatibility with Office PowerPoint 2007.

2

1

1203

Microsoft Script Editor data

When opening this file, Office PowerPoint 2007 discards MSE data that was stored on shapes, and saving removes it permanently. Solutions that depend on this data might break.

1

1

1204

Presentation broadcast data

When opening this file, Office PowerPoint 2007 discards configuration settings for HTML broadcast presentations, and saving removes it permanently. To broadcast in a previous version, the user must manually reenter the settings.

1

1

1205

Document routing

When opening this file, Office PowerPoint 2007 discards routing information, and saving removes it permanently. To route the presentation in an earlier version, the user must manually reenter the routing information.

1

1

1206

Publish and subscribe data

When opening this file, Office PowerPoint 2007 discards Macintosh Publish and Subscribe information, and saving removes it permanently. If reopened in a previous version, the Publish and Subscribe feature will no longer function.

2

1

1207

Large number of OLE objects

This file contains a large number of embedded objects. This can create security, fidelity, performance, and solution compatibility issues. Check this file for compatibility with Office PowerPoint 2007.

2

1

1300

Open format not supported

This file format will not open in Microsoft Office Excel 2007.

1

1

1301

Save format not supported

Office Excel 2007 does not support saving to this file format.

2

1

1302

HTML will be a publish-only file format

The HTML file format will be a publish-only file format in Office Excel 2007. The file will open in Office Excel 2007, but on save to an Office Excel 2007 format, the file will be static.

1

1

1303

Links in workspace files might be broken

A workspace file (.xlw) might contain links to other workbooks. The .xlw file might be broken if the links are changed during an upgrade.

3

1

1304

File format is prior to Excel 97

File format is prior to Excel 97. Such files are not scanned for migration.

2

1

1305

SharePoint linked lists in the file

Linked lists are read-only in Office Excel 2007.

2

1

1306

Microsoft Script Editor present in the file

Microsoft Script Editor (MSE) has been removed in Office Excel 2007. There will be no UI access to MSE, and object model calls will return an error.

1

1

1307

Linked workbooks in the file

Linked workbooks are indentified to help identify upgrade issues. The path to the linked workbook and the number of occurrences are identified. Linked workbooks will have different extensions when converted to the Office Excel 2007 file format.

2

1

1308

Charts in the workbook

Charts might not render the same as Excel 2003 in Office Excel 2007.

3

1

1309

English Language Formulas in the workbook

English Language Formulas (ELFs) are turned on. ELFs have been removed in Office Excel 2007, but all ELFs will be changed to cell references so they can continue to work in Office Excel 2007.

3

1

1310

Embedded documents in the file

Embedded documents are not scanned for compatibility issues.

2

1

1311

MSOWC.dll is referenced

This file uses features of the Office 2000 Web Components (MSOWC.dll). The Office 2000 Web Components will not be installed as part of the 2007 Office system and might need to be installed separately.

3

1

1312

OWC10.dll is referenced

This file uses features of the Office XP Web Components (MSOWC.dll). The Office XP Web Components will not be installed as part of the 2007 Office system and might need to be installed separately.

3

1

1313

OWC11.dll is referenced

This file uses features of the Office 2003 Web Components (MSOWC.dll). The Office 2003 Web Components will not be installed as part of the 2007 Office system and might need to be installed separately.

3

1

Review Office 2007 Compatibility

  1. On the OMPM Welcome page, select Office 2007 Compatibility. This brings up the Office 2007 Compatibility page.

  2. You can load a filter that you previously saved by clicking the Load Filter… button at the bottom of the page. Otherwise, specify your file filter settings in Select a File Filter, along the left side of the page.

    NoteNote:

    Filters apply to which files are shown, not which issues or created files are shown. For example, if you set Select Issues of Specified Type: to select all issues of level Red, all files with red issues appear. However, if those files also have yellow and green issues, reports of those issues also appear.

  3. To invert the filter for a specific setting, check the box to the right of the setting. For example, if you select a scanner run, you see all files discovered during that scanner run. If you invert the filter for that setting, you see all files discovered during other runs, but not during the selected run.

  4. To apply the filter, click the Apply Filter button at the top of the 2007 Office release Compatibility page. Use the tabs on the right side of the page to perform the following steps.

  5. Select the Issue Summary tab to view a summary of the issues identified by the OMPM File Scanner by severity, type, and frequency. You can bring up the summary in a new window by clicking New Window at the bottom of the page.

  6. To view issues and edit their severity level, click Manage Issues at the bottom of the Issue Summary page, and review or edit issues on the resulting Manage Issues dialog. If you review the impact of an issue and the issue is not important for your document set, you can also change the issue level in this dialog. You can use this to organize your files into processing groups of red, yellow, and green status.

  7. Select the Computer Summary tab to view a summary of the issues for each computer that was scanned. You can bring up the summary in a new window by clicking New Window at the bottom of the page. To obtain a printable report, click Report View at the bottom of the page.

  8. Select the Scanned Files tab to view files that match the criteria set by the filter you applied. You can bring up the summary for all files in a new window by clicking New Window at the bottom of the page. To obtain a printable report, click Report View at the bottom of the page.

  9. Select the Created Files tab to view files that were created using the Office File Converter or Version Extraction Tool. You can bring up the summary for all files in a new window by clicking New Window at the bottom of the page. To obtain a printable report, click Report View at the bottom of the page.

  10. To save the filter, click the Save Filter… button at the bottom of the page.

  11. Export the files to an XML file for use by the Office File Converter or Version Extraction Tool by clicking the Export… button at the bottom of the page.

For more information about the filter criteria you can select, see OMPM Reports filtering reference.

Review Access Compatibility

  1. On the OMPM Welcome page, select Access Compatibility. This brings up the Access Reporting page.

  2. On the Access Reporting page, look at the date of the last analysis (next to Analyze). If you have run a scan since that date, or if you have never run Analyze, click Analyzer Settings on the Access Reporting page, specify the settings that you want, and click Analyze. If you don't need to configure the settings and want to start an analysis of the scan data, click Analyze on the Access Reporting page.

    NoteNote:

    Clicking Analyze prompts you with the message "Analysis can take quite a long time and should not be canceled mid-run. Are you sure you want to continue?" If your scan data covers fewer than 100,000 databases, the analysis usually takes only a few minutes. If there are more than 100,000 databases, the analysis can take a long time, and you might prefer to run the analysis overnight.

  3. To search the Access scan data by field, select QuickSearch on the Access Reporting page. This lists files that OMPM has analyzed. Use QuickSearch to find a specific database file by name, or a list of databases in a specific path or on a specific computer.

  4. To view or print interactive reports for Access data, select Reports on the Access Reporting page. This brings up the View Reports tab. On the left navigation pane, you can choose from the following reports:

    • Database and Issue Details. Use this report to get the list of issues for each database file.

    • Database Issues Grouped by Issue. Use this report to find all the databases that are identified as having a specific issue.

    • Executive Summary. This report provides an overview of issues for all analyzed databases, without the file-level details.

    • Active versus Old Databases. This report lists analyzed databases and shows whether they are active or inactive, based on their LastModified property.

    • Conversion Issue–Database is an MDE file. This report lists .mde files and .mdb files that have identical names.

    • Conversion issue–Replicated database. This report lists databases that use replication.

    • Conversion issue–Reserved name in Form/Report/Macro. This report lists databases that contain a reserved name in a form, report, or macro.

  5. To view interactive charts that facilitate finding databases with certain attributes, select Charts on the Access Reporting page. This brings up the Database Charts screen, where you can choose from the following charts:

    • Date Last Opened. Database count per year opened.

    • Database Rating. Database count by level of user intervention required.

    • Access Version. Database count by version of Access.

    • File Size. Database count by file size.

    • Conversion Issues. Database count by conversion issue.

    • Warning Level. Database count by warning level.

  6. To view databases and database objects on a per-file basis, data, select File Details on the Access Reporting page.

  7. To view database issues on a per-file basis, data, select Conversion Issues on the Access Reporting page.

    The following table is a list of all the OMPM Access Errors:

    Issue IDIssue TextUser InterventionIssue TypeUser Intervention Priority

    1

    Too many code or class modules

    Required

    Error

    1

    2

    Sort Order and System Language do not match

    Likely

    Warning

    2

    3

    Replicated Database

    Required

    Warning

    1

    4

    Database is an MDE file

    Required

    Error

    1

    5

    DAO 2.5/3.5 compatibility layer

    None

    Note

    3

    6

    Microsoft Jet SQL help

    None

    Note

    4

    7

    Additional References

    Likely

    Warning

    2

    8

    Missing References

    Likely

    Warning

    2

    9

    Reserved Name in Form/Report/Macro

    None

    Note

    4

    10

    Linked Tables

    Unlikely

    Warning

    3

    11

    Database in uncompiled state

    None

    Note

    4

    12

    Backup database

    None

    Note

    4

    13

    Sample database

    None

    Note

    4

    14

    Old database

    None

    Note

    4

    15

    Secure database: User Level Security

    Likely

    Error

    2

    16

    Secured database: Database password

    Likely

    Error

    2

    17

    System database

    None

    Note

    4

    18

    Unsupported legacy format

    Likely

    Warning

    2

    19

    Unsupported legacy format – forms, reports, and modules will be lost

    Required

    None

    1

    Errors 1–17 are the complete list of errors that can be generated by the Access Conversion Toolkit. Documentation for 1–17 can be found in the Access Conversion Toolkit. The documentation is Flash-based and requires the installation of the toolkit. To install the toolkit, see Access 2003 Conversion Toolkit (http://go.microsoft.com/fwlink/?LinkId=131929).

    Errors 18 and 19 are new to OMPM and mean:

    • Error 18 – Microsoft Office Access 2007 no longer opens files created in Access 2.0.

    • Error 19 – Office Access 2007 will open a file that was created in Access 95, but will not read its forms, reports, or modules.

Download this book

This article is included in the following downloadable book for easier reading and printing:

See the full list of available books at Office Resource Kit information.

See Also

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft