- Introduction
- The Goal
- Creating the Web Interface
- The Office Macro
- Parting Thoughts
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
The Office Macro
The Microsoft Word side of this solution is pretty straightforward. To begin, I've added a few macros to the Normal template (normal.dot) to handle saving the document to the server and then kicking off the upload process on the server. To move the document from the workstation to the server, I've created a web share on my CMS server to receive the documents.
Since Office 2000 and XP both natively support saving to web shares, we can use the standard SaveAs method to save the document to the web share location and then back to the original location. Saving back to the original location is just a courtesy to the user, thereby preserving the document's original file location and name.
Here's what's happening on the Office side:
The user is prompted to enter the description of the document, if it doesn't already exist (see Figure 1). Later, we'll pass this description to CMS for the Posting.Description property.
Figure 1 Document description.Once the user has entered a description, we'll save the document to the web share on the server. In this example, the web share is set up for write access only, thereby preventing the casual user from examining the share outside of our application.
After saving the document to the repository, we'll save it back to the original location, so that we don't change the actual location of the document.
Now, we'll kick off the ASP interface to perform all of the CMS functions.
)
Figure 1