Microsoft KB Archive/162823: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
Line 49: | Line 49: | ||
Advanced: Requires expert coding, interoperability, and multi-user skills.<br /> | Advanced: Requires expert coding, interoperability, and multi-user skills.<br /> | ||
<br /> | <br /> | ||
This article assumes that you are familiar with using the client side capabilities of Microsoft Visual SourceSafe. For more information about Visual SourceSafe, please refer to the | This article assumes that you are familiar with using the client side capabilities of Microsoft Visual SourceSafe. For more information about Visual SourceSafe, please refer to the "Visual SourceSafe User's Guide" or the Help topics available from the Visual SourceSafe menu.<br /> | ||
<br /> | <br /> | ||
Microsoft Access and Visual SourceSafe Integration do not use the Office Assistant character when alerting you of errors or information. | Microsoft Access and Visual SourceSafe Integration do not use the Office Assistant character when alerting you of errors or information. |
Latest revision as of 11:01, 21 July 2020
Article ID: 162823
Article Last Modified on 2/12/2007
APPLIES TO
- Microsoft Access 97 Standard Edition
- Microsoft Visual SourceSafe 4.0 Standard Edition
- Microsoft Visual SourceSafe 4.0a
- Microsoft Visual SourceSafe 5.0 Standard Edition
This article was previously published under Q162823
SYMPTOMS
Advanced: Requires expert coding, interoperability, and multi-user skills.
This article assumes that you are familiar with using the client side capabilities of Microsoft Visual SourceSafe. For more information about Visual SourceSafe, please refer to the "Visual SourceSafe User's Guide" or the Help topics available from the Visual SourceSafe menu.
Microsoft Access and Visual SourceSafe Integration do not use the Office Assistant character when alerting you of errors or information.
CAUSE
Visual SourceSafe is not a component of Microsoft Office and because of the large number of other Microsoft products and development environments that Visual SourceSafe integrates with, it retains its own internal specifications for messages and alerts.
STATUS
This behavior is by design.
MORE INFORMATION
There are error messages that you may receive while using Visual SourceSafe that do use the Office Assistant character; however, these messages may be generated by Microsoft Access 97 or the Microsoft Jet 3.5 database engine, rather than by Visual SourceSafe.
Keywords: kbprb KB162823