Microsoft office code compatibility inspector access

Was this reply helpful? Yes No. Sorry this didn't help. Thanks for your feedback. If you're comfortable with it, you can post the file to OneDrive, and share the link. Just make sure to remove any sensitive company or personal information. As I began this thread, ideally we need to be able to run this on Excel 64 bit , as well as on older 32 bit systems.

Since we are all independent contractors, everyone makes their own decisions as to when to purchase computers, and what configuration to purchase. Compile error. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question 0. In this article. Most recently used Office documents and installed add-ins on this computer.

The Readiness Report Creator only scans Office documents that are in the user's list of most recently used files. This allows you to narrow the focus of the scan to documents that a user accesses on a regular basis. In addition, the Readiness Report Creator looks for any add-ins for Office that are installed on the computer on which the Readiness Report Creator is run. The Readiness Report Creator scans the Office documents in the folder or network share that you specify.

The Readiness Report Creator automatically scans the specified location, and all the subfolders in that location. Note: With this option, the Readiness Report Creator doesn't look for add-ins installed on the computer on which the Readiness Report Creator is run. Previous readiness results saved together in a local folder or network share. This option allows you to create a consolidated report comprised of individual readiness results from multiple standalone computers.

For example, you might want to run the Readiness Report Creator on all the computers in the Finance department, saving the results of each scan to a network share. Then, you can use this option to create a consolidated report for the Finance department. If you're already using Office Telemetry Dashboard to assess add-in compatibility, you can use that information which you've already collected to create a readiness report.

You just need to provide the Readiness Report Creator with the appropriate information to access the database for Office Telemetry Dashboard. Displays three pie charts to provide a high-level overview of the results of the scan. Each pie chart shows different information: the status of the files scanned, the readiness status for the unique macros found during the scan, and readiness status of the unique files scanned.

See the tables later in this section for more information about the file status and readiness status values that appear in these pie charts.

The Readiness Toolkit creates a unique hash of the VBA macro code to identify macros that are reused in multiple files. The Readiness Toolkit does something similar to identify duplicate files. The Readiness Toolkit does this to provide you with a more realistic assessment of how many unique VBA macros and unique files need to be evaluated. Note: If you plan to deploy the bit version of Microsoft Apps, be sure that the "Include bit readiness data" check box is selected and that you've refreshed the report.

Provides some pre-defined PivotTables to allow you to analyze the data captured from the scan. If these PivotTables don't meet your specific needs, you can create your own based on the data on the VBA Results worksheet.

Provides information on each file scanned by the Readiness Report Creator. If multiple issues are found in a scanned file, there is a separate row for each issue. See the table under the "Detailed VBA information" heading at the end of this section for an explanation of the information that appears in each column. Provides proposed changes to VBA macro code found during the scan. List references identified in code and in the VBA project.

The file couldn't be scanned because it is saved in a SharePoint document library, in OneDrive, or in some other type of cloud-based storage location. The file is password protected so it couldn't be scanned for VBA macros.

The file couldn't be scanned for some reason, such as the Readiness Report Creator had insufficient permission to access the file, the file is corrupted, or the file uses a very old Office file format. The file couldn't be scanned because the required Microsoft Access Database Engine isn't installed on the computer performing the scan.

The VBA code stream trying to be read during the scan wasn't in a valid format. Sometimes opening, and then saving, the file in a supported Office version will allow the Readiness Report Creator to scan the file.

No issues were found in this file and it's compatible with Microsoft Apps. While the code will function as expected and the user isn't likely to notice any change, the feature, property, or method works differently than previously or might be deprecated in favor of a newer version. No runtime or compile time errors are expected, but the API functionality may have changed in some way. It's recommended that the user runs a spot check on the file with Microsoft Apps to ensure it continues to function as expected.

To minimize environmental issues, ideally run the spot check on the computer that the macro usually runs. Some refactoring of code will be required. But, there is a clear replacement and so the expectation is that the work required to fix the macro is significantly reduced. Significant code refactoring will be required to enable the code to continue to function as it did in the legacy Office version. For example, an API that has been deprecated, but no replacement function has been provided.

In this case, the only option available is to recreate the functionality. The guideline rule identified when document has been scanned. Program Toolbars and Menu Bars will no longer be visible in Access VBA Module section name where the issue was identified that is, function.

Link to description of issue and help content where applicable. VBA code found in the macro, which may cause issues when moving to a bit version of Office. Suggestions on how the VBA code in the macro can be updated to work correctly with a bit version of Office. Value of custom label, if configured. For more information, see Use labels to categorize and filter data in reports. Unique value used to identify the file name in the file-names.

For more information, see Manage the privacy of data collected in reports. Version of the Readiness Toolkit installed on the computer running the scan. Provides a high-level overview of the add-ins found by the Readiness Report Creator. The data at the top of the worksheet is intended to give you a quick assessment of how many add-ins will likely be compatible with Microsoft Apps and how many add-ins you'll need to do more research on.

Provides metadata information about the add-ins found for example, publisher and version number , the total number of installs of each add-in, and, if an advanced report, the readiness status for example, "Supported version available". Provides similar information to what's on the Add-in Details worksheet, but lists every computer that the add-in is installed on, instead of just a total number of installs for the add-in.

This add-in is being widely used on Microsoft Apps in other organizations, and is ready for use with Microsoft Apps. But, the software provider doesn't officially support the add-in on Microsoft Apps. This add-in is being used on Microsoft Apps in other organizations, but the software provider doesn't officially support the add-in on Microsoft Apps.

This add-in might have issues with Microsoft Apps. You need to decide if this add-in is business critical and then contact the software provider for guidance. A supported version of this add-in for Microsoft Apps is available from the software provider. This add-in is unknown to Microsoft. For example, it could be a line-of-business add-in that your in-house application development team created.

If you create a basic report, the readiness status for all add-ins is listed as Unknown. It's only when you create an advanced report that the Readiness Report Creator contacts Microsoft to try to get readiness status of add-ins. Microsoft has seen this add-in but not enough information has been collected to provide a readiness status for this add-in. The name of the computer on which the add-in is installed.

This column only appears on the "By computer name" tab. The Office application that the add-in is used in. For example, Word or Excel. The total numbers of installs of the add-in. This column only appears on the "Add-in Details" tab. The readiness status for the add-in. Advanced reports only.

See the table above for a list of possible readiness statuses. Note: If you chose "bit" from the drop-down list on the "Add-in Summary" tab, this column name displays as " bit " instead. Additional information, if available, about the readiness status of the add-in. Link to additional readiness information about the add-in. Number of devices on which the add-in is installed. Available when collecting add-in usage information.

For more information, see Collect and show add-in usage information in reports. Number of devices on which the add-in has been used since you started collecting add-in usage information.

Indication of whether the add-in has been used since you started collecting add-in usage information. Excel-supported automation add-ins are built upon COM add-ins. Functions in Automation add-ins can be called from formulas in Excel worksheets. These include macro-enabled Word templates.

XLL add-ins. They do not have to be installed or registered. Count of how many times a specific rule was found to apply to the VBA macros scanned. A GUID is used to uniquely identify the rule. Count of unique files that contain use of features that we would recommend changes. Number of devices scanned that included macros that used Declare statements. Number of devices that contain macro files that require significant remediation. Number of devices that contain macros that require remediation to be unblocked from upgrading to Microsoft Apps.

Number of devices that contain macro files that require limited remediation. Number of devices that contain macro files that require minimal validation. You won't get application event data for these clients like you do with newer Office clients, but you'll get inventory and usage data that helps you discover what is being used and likely important to your business.

The Office compatibility tools address common issues that can make Office deployments difficult. These tools help by speeding up deployments, reducing the unknown factors in your deployment through reporting, and laying a foundation for future Office upgrades. For the best results, use the compatibility infrastructure that's built into Office and use a phased approach to assess Office compatibility.

In this article, we'll discuss each phase of the compatibility process and describe how you can use Office Telemetry Dashboard to support the process. Your goal for the Discover phase is to know what's being used the most and by whom. There are two approaches that you can take to start the discovery process. The preferred approach is to start to deploy the Office Telemetry Agent to help you discover usage within monitored groups and then use those results to begin discussions with business groups.

Another option is to partner with your business groups and ask them for a list of their business-critical documents and solutions. If they have a disaster recovery plan, you can likely find this list in their plan. The downside to this approach is that their lists might not be up-to-date.

You should plan to use data to help refine these lists if you choose this approach. Whether or not you start with a blank list, there is no avoiding working with your business groups. The tools can't tell you what's important to the business. The tools can give you some leads on what's important based on use, but only the business groups can tell you how dependent their business is on those documents and solutions. For example, if you only base your work on data, you might miss seasonally used solutions, such as year-end sales reports or annual performance review templates, or other documents that aren't being used at the time that you collect data.

Now it's time to start to make plans to deploy the agent to the existing Office clients. Here are some considerations to think about before you deploy the agent. You will find requirements to deploy the agent in Office Telemetry Agent. This sample should include representative users from every business group so that you can identify line-of-business solutions that are used within pockets of the organization.

Make sure to include expert users in that sample and users who express interest in piloting Office. There might be cases in which monitoring a complete group or organizational unit OU is less restrictive or easier than selecting separate client computers to participate.

Small organizations might also choose to monitor all client computers. Some business groups, such as human resources, legal, and finance, might have concerns about exposing personal or sensitive files in the data. Office Telemetry Dashboard offers several ways to prevent exposing this data. For example, you can configure the agent to intentionally obscure file names and titles.

You can also prevent data from certain applications from being reported. You can learn more about the privacy settings in Manage the privacy of data monitored by Office Telemetry Dashboard. Review the privacy options with the business groups and decide which kinds of Office data that you want to exclude from reporting in Office Telemetry Dashboard. When you deploy the agent to clients, you can specify up to four labels that describe the clients.

These labels help you filter data in the dashboard so that you can focus on individual business groups, specific kinds of users, users in certain geographical locations, and so on. Develop this list as you work with business groups. You can learn more about how to configure labels when you Deploy Office Telemetry Dashboard , in the section Enabling and configuring the agent.

The goal of the Rationalize phase is to identify business-critical Office documents and solutions. We recommend that you collect data in Office Telemetry Dashboard for at least one day before you start to look for trends.

The sections that follow will help you interpret the data, work with business groups, and decide what to test. As data starts to populate in Office Telemetry Dashboard, you can start to look for usage trends.

Here are some tips to get you started. Look to see whether any departments or groups are not represented but should be. For example, if there are no finance solutions being used, you might have forgotten to enable monitoring for the finance group. These are candidates for additional evaluation. Look for documents that are used by 3 or more users. Is there a trend for co-authoring? Are these templates? You might find that fewer documents are shared than solutions.

Jot down solutions that you know are very important that you will want to track in the future even if the user numbers are low. Look to see where documents were opened from. This can help you differentiate between an attachment in an email message and a frequently edited document. Look for multiple file sizes of the same solution or document. This could indicate that multiple versions are being used.

These are candidates for future consolidation. At this point, you may have already worked with business groups to identify their critical documents and solutions.

Compare the list they gave you with the usage data that's shown in Office Telemetry Dashboard. Does the usage data support the input from the business groups? If not, could there be a seasonal explanation? For example, are some solutions used more towards the end of the fiscal year? It's worth having another conversation with business groups about any differences you find so that you can adjust your plans for user acceptance testing.

If you haven't worked with business groups yet, this is the time to approach them. The initial usage data can help you create a list of documents and solutions that are candidates for testing and remediation. But instead of assigning priority levels, such as high, medium, or low, it's better to rank documents and solutions by the type of testing they will undergo.

Ask your business groups to assign them to one of the choices in the following table:. When you approach business groups to classify their documents and solutions, you might meet some resistance from business groups that assign everything to the high priority list.

One of our Office compatibility experts, Chris Jackson, wrote an article for TechNet Magazine that describes some costs behind Office compatibility testing.