microsoft.com Home | |||
http://www.microsoft.com/office/ork |
Customizing Built-in Error MessagesCreating Custom Error MessagesThe task of creating and implementing your own custom error messages consists of the following four steps:
Note This process documents the use of an ASP page. If you want to use a Common Gateway Interface (CGI) script, refer to your CGI reference manual for more information about CGI script. At the end of this process, you have the following components:
To create custom error messages or to modify default error messages, you need to create a server-side script to handle the custom error messages. This script can be in either ASP or CGI code. You can create the server-side script by using the following tools: ASP generator If you are going to create a small number of custom error messages, you can use the ASP generator (an Excel workbook called ASPscrpt.xls) to create an ASP page. An ASP page is the best choice when you’re running Microsoft Windows NT® Server and Microsoft Internet Information Server (IIS). Toolbox The Office Resource Kit includes a file called ASPscrpt.xls to help you create your ASP script. Use this ASP generator to create the ASP file to handle your custom error messages. For information about installing this file, see Customizable Alerts. Sample ASP script There are also sample ASP pages and HTML files that you can modify to create your own ASP scripts. Toolbox The Office Resource Kit includes sample ASP scripts and HTML files to help you create custom error messages. Create your own ASP scripts and HTML files based on the files Alert.asp, Alert.htm, Alert2.asp, Alert2a.asp, and NYI.htm. For information about installing these files, see Customizable Alerts. Microsoft Visual Basic Scripting Edition or a CGI-based scripting tool You can also use Visual Basic Scripting Edition or a CGI-based scripting tool to create a server-side script. The script is used to process the error message numbers, GUID numbers, and country codes, and to return a Web page containing a solution for the user. |
|
Topic Contents | Previous | Next | Top Friday, March 5, 1999 © 1999 Microsoft Corporation. All rights reserved. Terms of use. | ||
License
|