Q060601a: Confirming ODMA-Aware Connection

Status	Date	Description



	2006-06-18	We need a complete FAQtip on how ODMA finds the default DMS for an application.
	2006-06-18	Q060601c Fig.4-1 needs image caption and eventually a link to something (e.g., more on ODMA Use of the Registry).
	2006-06-18	Q060601 0.10: Post to the ODMA site and announce on the UDP list.
	2006-06-18	Q060601c 7.3.2 Include links to any tips for developers on how to connect with the ODMA Connection Manager.
	2006-06-18	Q060601c 7.3.2 Include link to the registry of known ODMA-aware applications.
	2006-06-18	Q060601c 7.2: Good place to link to material on creating and interpreting logs too.
	2006-06-18	Q060601c 7.2: Add link to procedure for creating an application-specific default DMS.
	2006-06-18	Link Q060601c Section 6.3 to information on verifying the right version.
	2006-06-18	Verify that ODMATest32 will pass this confirmation.
	2006-06-17	Q060601c Setion 4.2.6: We need to check the ODMA32 implementation and make sure it doesn't do something silly in DLLMAIN about erasing an existing log. It should be part of ODMRegisterApp, and we should make that clear in descriptions of logging behavior.
	2006-06-17	Q060601c Section 4.2: At some point it needs to be pointed out that the ODMA 2.0 Connection Manager log does not include logging of COM interfaces that have been obtained through the Connection Manager. It doesn't have to be that way, but it is. Doing it at the COM level would also be a superior way to avoid testing for the log on each entry and constantly checking for logging when it is not needed.
	2006-06-17	Q060601c Section 4.2: Reference the logging section of the specification and also link to other resources on working with logs, including initiation of logging.
	2006-06-17	There should be separate procedures for setting application defaults and setting global defaults, and turning them on and off. These can all reference a separate document on registry operations and how to perform them from a limited account.
	2006-06-17	Q060601c 4.1.3 Include an image of a DMS default being removed and then restored.
	2006-06-17	Q060601c 4.1.3 Include reference to the specification for global default DMS. Include link information for how this is cleared and how it is restored.
	2006-06-17	Verify the ODMA Connection Manager behavior when there is more than one default ODMA DMS entry.
	2006-06-17	Verify the behavior for a Default DMS ID with a bogus entry.
	2006-06-17	Verify the behavior for a DMS ID with a bogus entry in an application default ODMA DMS entry.
	2006-06-17	Verify the ODMA behavior for a non-existent DMS ID in an application default ODMA DMS entry.
	2006-06-17	Q060601c 4.1.2: Get an image of an entry for an application, and then turn off the application default by renaming the key, if that works.
	2006-06-17	Q060601c 4.1.2: Include reference to the specification for default application DMS. Include link to information on how that is set and how that is eliminated.
	2006-06-15	Q060601c 4.1.1: Include references to the specification for ODMRegisterApp and also to anything explaining the log for ODMRegisterApp. Include this under Resources too.
	2006-06-15	Q060601c 3.3.2: Provide links to installing the ODMA SDK and the latest ODMA32.dll, etc. Refer to other FAQtips on this topic. Include under resources too.
	2006-06-15	Q060601c 3.3.1: There needs to be a way to disable ODMA completely if the application seems to be failing because ODMA is present. Provide a separate page on this. Also, it would be great to develop a DMS dll that simply rejects connections. Then it could be made the default for any applications for which ODMA operation is undesirable, while allowing ODMA for other ODMA-aware applications. There have been requests for a capability like that.
	2006-06-14	Q060601c 3.2: Provide links to resources on elevating an account, on using RunAs to adjust the registry, and on using Restore Points to protect the registry.
	2006-06-14	Q060601c 3.1: Add information on using the latest version of ODMA32.dll.
done 0.10 2006-06-18	2006-06-14	Q060601 0.10: Reflect in Q000001-log after everything is ready to update
done 0.10 2006-06-18	2006-06-14	Q060601: Update to 0.10 when Q060601c is updated enough for posting and review
not done 2006-06-17	2006-06-14	Do an OPML outline of the necessary steps and what I want to cover. [dh:2006-06-17 I am having enough difficulties with the OPML Editor beta version that I am not taking that option at this point. I'll get the kinds out of my OPML usage with some Getting Things Done practices, then see about providing them as backup elements for these web projects.
not done	2006-06-17	Q060601c: Section 4 needs to be flattened. It is only about making sure there is no default DMS to be found for this application. [dh:2006-06-17 My mistake. I forgot what I needed section 4.2 for. That's now fixed.]
done	2006-06-14	Q060601: Add permalinks and section contents to the cover page material
done	2006-06-14	Customize Q060601c placeholder ready for more material based on the Q060601 summary/sketch
done	2006-06-14	Make Q060601b as an include-page for Q060601c
done	2006-06-14	Create this page ready for recording Diary & Job Jar items of this FAQtip.
done	2006-06-14	Make simple placeholder for the folio cover