This response addresses questions about integration of Microsoft Office applications in ODMA configurations:
Components of Microsoft Office have been ODMA-aware since Office 97 was released.
The components that have consistently supported ODMA are
- Microsoft Word
- Microsoft PowerPoint
- Microsoft Office Binder
Other applications, such as Microsoft Excel, have not been integrated with ODMA as of Microsoft Office 2000.
The implementation of ODMA-aware document access appears to be limited to the components that use the same shared implementation of file-access dialogs and code.
- see also:
- X000600: Word 2000 + ODMA32 + SampleDMS
On Windows NT 4.0 and all recent versions of Win32 platforms (Windows 98, Windows 98 SE, etc.), Microsoft Office is configured to operate in Unicode by default.
The ODMA Connection Manager and ODMA DMS Integrations are not Unicode-enabled. This applies to all implementations of the ODMA specification from ODMA 1.0 to ODMA 2.0.
When a Unicode-based Microsoft Office application is also ODMA-aware, one of two symptoms will occur:
- Even though the application is ODMA-aware, all File menu dialogs ignore ODMA and offer file-system access only.
- ODMA and the DMS are accessed, but no matter what DMS document the user selects, the application reports that it is seeing an invalid file name.
Microsoft provides registry settings that cause Microsoft Office applications to communicate over the ODMA API using the ANSI character code supported by ODMA.
Presence of the following Windows Registry key causes Microsoft Office to operate correctly with ODMA:
This registry key applies on any Win32 platform, not just Windows NT.
Modification of a registry key is required to configure Microsoft Office to operate with ODMA in the ODMA-accepted character set.
On some configurations (e.g., Windows XP, Windows 2000) you will require administration privileges to perform the modifications.
The change, if correctly made, is harmless on a configuration where Microsoft Office does not require the registry information or where ODMA is not being used. The change can be safely made anytime there are symptoms of the kind described above (section 1.2).
Download the short text file
Or manually create the file with the following text and then save it with name
In Windows, find the file
msodma.regwhere you placed it.
Double-click on the file name or icon.
The Registry should be updated automatically.
Restart your machine to ensure that the configuration of Microsoft Office will be adjusted the next time an Office application is started.
If difficulties persist, review the suggestions in section 3, Other Conditions to Check.
To perform the registry adjustments automatically, perform the following steps:
Open the Microsoft Windows Registry Editor,
Open the Start Bar menu Start | Run ...
When the registry tree is presented, expand down the path
If the full path is not present, add new keys until it is.
There is no default value required for
ANSIonNT. It is sufficient that there is the key.
- see also:
- Q000603: Latest ODMA Software
If Microsoft Office does not operate with ODMA after the registry key is set, check the following conditions:
Make sure that there is a current version of
Windows\SYSTEMdirectory (as named in your Win32 configuration).
Make sure that a global default DMS is specified.
Make sure that, if there is a separate default DMS assigned for the MS Office component, the registry entry for that assignment is correct and there is a correct registry entry for the ODMA32 DMS:
The ODMA Application ID for Microsoft Word is "
The ODMA Application ID for Microsoft Powerpoint is "
Check the Microsoft Knowledge Base (Using ODMA as a search key) for any new information about ODMA Support. For example, the procedure of this FAQtip is described at
Check other resources for support information about Microsoft Office applications for tips and information about MS Office and ODMA.
- Robert Barham (0.10)
- 1999-01-28 contributed the procedure and an e-mail explanation for configuring Word97.
- Jonathan Cecil (0.10)
- confirmed, with Microsoft Knowledge Base reference, that Word 2000 and configurations on Windows 2000 tend to fail rather than just ignore ODMA when ANSI communication with ODMA is not selected in the registry. This resolved X000600 too.
- Jonathan Cohen (0.15)
- requested clarification about the versions of Windows that this applies for, as well as requesting a tool to make the change
- Dennis Hamilton (0.10)
- (0.10) researched the question and compiled the FAQtip from the earlier contributions. (0.20) Dennis later confirmed the Office 2003 behavior, how to troubleshoot the connection of Office 2003, and identified the Office 2003 components that are ODMA-aware.
- Colin O'Brien (0.10)
- provided the registry correction procedure through his first ActiveDoc ODMA FAQ page.
- S. Ramanathan (0.10)
- reported X000600 and confirmed that it is resolved by re-configuration of MS Office to use ANSI instead of Unicode.
.regfile can be used to make the change.
ODMA Interoperability Exchange.
created 2000-10-19-08:16 -0700 (pdt) by orcmid