Article ID: 180838
Article Last Modified on 11/23/2006
APPLIES TO
- Microsoft Outlook 98 Standard Edition
This article was previously published under Q180838
SUMMARY
This article describes troubleshooting tips that you can use when an Outlook programming solution works on your development computer, but does not work properly on another person's computer.
MORE INFORMATION
Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support professionals can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs. If you have limited programming experience, you may want to contact a Microsoft Certified Partner or the Microsoft fee-based consulting line at (800) 936-5200. For more information about Microsoft Certified Partners, please visit the following Microsoft Web site:
For more information about the support options that are available and about how to contact Microsoft, visit the following Microsoft Web site:
Use the following troubleshooting tips to solve problems with your programming solution.
VBScript Version
If your solution involves forms that use Visual Basic Scripting Edition (VBScript), you may need to make sure that all computers are using the same version of VBScript that is being used on your development computer. For example, if you used a "For Each...Next" programming construct in VBScript 2.0, you must install VBScript 2.0 on all computers because VBScript 1.0 does not support these commands.
For more information about VBScript versions, please see the following article in the Microsoft Knowledge Base:
182446 OL98: General Information About Using VBScript with Outlook
Controls
If your solution uses any controls, check to see if the controls are properly installed on all user computers. Are they the same version? Ideally, unless you are only using the "Forms 2.0" controls that are installed by Microsoft Office, you should require your users to run a setup program to make sure all of your controls are installed correctly. Both Visual Basic and Office 97 Developer Edition include tools to create custom setup programs.
Permissions or User Rights
Make sure that any user experiencing problems has proper permissions or rights to use any public folders or other resources that your solution uses.
Send Form Definition with Item
If your solution sends forms from one user's computer to another, did you enable the "Send form definition with item" option on the form's Property tab when in design mode? If not, you or the users must properly install the form so that it is available for the other users.
Read Layout
By default, mail message forms have separate Compose and Read pages. If you want the form to have one view when it is created or read, turn off the Separate Read Layout setting on the Layout menu when the form is in design mode. Depending on the type of form, this setting may be on or off by default.
REFERENCES
For more information about creating solutions with Microsoft Outlook 98, please see the following articles in the Microsoft Knowledge Base:
180826 OL98: Resources for Custom Forms and Programming
182349 OL98: Questions About Custom Forms and Outlook Solutions
Additional query words: OutSol OutSol98 machine
Keywords: kbprogramming kbsetup KB180838
