DOCUMENT:Q191792 01-SEP-1998 [vbwin] TITLE :INFO: VB 6.0 Readme – Part 13: Dictionary Object PRODUCT :Microsoft Visual Basic for Windows PROD/VER: OPER/SYS: KEYWORDS: ====================================================================== ------------------------------------------------------------------------ The information in this article applies to: - Microsoft Visual Basic Learning, Professional, and Enterprise Editions for Windows, version 6.0 ------------------------------------------------------------------------ SUMMARY ======= The information below includes the documentation and workarounds for Visual Basic 6.0. This information can also be found in the README.htm file that ships with Visual Basic 6.0 on the Visual Basic 6.0 CD-ROM. Please see the REFERENCES section of this article for a list of the Microsoft Knowledge Base articles relating to the Visual Basic 6.0 readme. Following is a list of all parts of the readme file: Part 1. Important Issues – Please Read First! Part 2. Data Access Issues and DataBinding Tips Part 3. Control Issues Part 4. Language Issues Part 5. Samples Issues Part 6. Wizard Issues Part 7. Error Message Issues Part 8. WebClass Designer Issues Part 9. DHTML Page Designer Issues Part 10. Extensibility issues Part 11. Miscellaneous Issues Part 12. Microsoft Transaction Server (MTS) Issues Part 13. Dictionary Object Part 14. Visual Component Manager Part 15. Application Performance Manager MORE INFORMATION ================ Introducing the Dictionary Object --------------------------------- Visual Basic 6.0 includes a new Dictionary object that can be used instead of a Collection object or an Array. A Dictionary object is the equivalent of an associative array as used in PERL and other languages. The Dictionary object provides additional properties and methods that aren't available for Collections or Arrays. The Dictionary object is contained in the Microsoft Scripting Runtime (Scrrun.dll) that ships with Visual Basic 6.0. You must add a reference to Scrrun.dll in order to use the Dictionary object in your project. To learn more about the Dictionary object, search online, with Search titles only selected, for "Dictionary Object" in the MSDN Library Visual Studio 6.0 documentation. REFERENCES ========== For additional information, please see the following articles in the Microsoft Knowledge Base: ARTICLE-ID: Q170164 TITLE : INFO: VB 6.0 Readme – Part 1: Important Issues – Read First! ARTICLE-ID: Q170163 TITLE : INFO: VB 6.0 Readme – Part 2: Data Access/Databinding Issues ARTICLE-ID: Q170162 TITLE : INFO: VB 6.0 Readme – Part 3: Control Issues ARTICLE-ID: Q170161 TITLE : INFO: VB 6.0 Readme – Part 4: Language Issues ARTICLE-ID: Q170160 TITLE : INFO: VB 6.0 Readme – Part 5: Samples Issues ARTICLE-ID: Q190046 TITLE : INFO: VB 6.0 Readme – Part 6: Wizard Issues ARTICLE-ID: Q170158 TITLE : INFO: VB 6.0 Readme – Part 7: Error Message Issues ARTICLE-ID: Q189539 TITLE : INFO: VB 6.0 Readme – Part 8: WebClass Designer Issues ARTICLE-ID: Q190249 TITLE : INFO: VB 6.0 Readme – Part 9: DHTML Page Designer Issues ARTICLE-ID: Q170154 TITLE : INFO: VB 6.0 Readme – Part 10: Extensibility Issues ARTICLE-ID: Q170157 TITLE : INFO: VB 6.0 Readme – Part 11: Miscellaneous Issues ARTICLE-ID: Q170156 TITLE : INFO: VB 6.0 Readme – Part 12: Transaction Server (MTS) Issues ARTICLE-ID: Q191791 TITLE : INFO: VB 6.0 Readme – Part 14: Visual Component Manager ARTICLE-ID: Q191790 TITLE : INFO: VB 6.0 Readme – Part 15: Application Performance Explorer Additional query words: kbVBp600 kbVS600 kbMSDN kbReadme ====================================================================== ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 1998.