While no CDO was used in the original CML application, the ASP pages of the combined CML/LitCrit application use CDO to support critique functionality. In the CML application itself, CDO reads critique text that the application displays on the CML Display Critique page; see Reading a Critique from the CML. In addition, the OutlookŪ HTML Form Converter uses CDO liberally in the ASP pages it generates. Two of the central pages generated for the LitCrit application are:
Most of the code in these files is HTML that displays the forms' user-interface elements. Much of the scripting code, however, involves CDO. This CDO code was not written by the F & M developers who created the LitCrit Web form; rather, it was all created automatically during form generation. Moreover, the CDO code in the generated form's ASP pages is not derived from the original form's script (that script is not carried over to the converted form), but instead is generated from scratch to perform basic actions required by the form.
As described in the next topic, the CDO Rendering Library is used in the ASP pages of the Web version of the LitCrit form to display user-interface elements.
The frmRoot.asp file creates a new message with the following code:
Set objOneMsg = objFolder.Messages.Add(bstrSubject,,"IPM.Post.EnhancedLitCrit")
Set Session(bstrObj) = objOneMsg
AddIDToCache(bstrObj)
After the message object is created, it is stored in the ASP Session object until the form is closed.