DOCSLIB.ORG

[MS-OAUT]: OLE Automation Protocol

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
[MS-OAUT]: OLE Automation Protocol [MS-OAUT]: OLE Automation Protocol Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected]. License Programs. To see all of the protocols in scope under a specific license program and the associated patents, visit the Patent Map. Trademarks. The names of companies and products contained in this documentation might be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit www.microsoft.com/trademarks. Fictitious Names. The example companies, organizations, products, domain names, email addresses, logos, people, places, and events that are depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred. Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than as specifically described above, whether by implication, estoppel, or otherwise. Tools. The Open Specifications documentation does not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments, you are free to take advantage of them. Certain Open Specifications documents are intended for use in conjunction with publicly available standards specifications and network programming art and, as such, assume that the reader either is familiar with the aforementioned material or has immediate access to it. Support. For questions and support, please contact [email protected]. 1 / 195 [MS-OAUT] - v20210625 OLE Automation Protocol Copyright © 2021 Microsoft Corporation Release: June 25, 2021 Revision Summary Revision Revision Date History Class Comments 12/18/2006 0.1 New Version 0.1 release 3/2/2007 1.0 Major Version 1.0 release 4/3/2007 1.1 Minor Version 1.1 release 5/11/2007 1.2 Minor Version 1.2 release 6/1/2007 1.2.1 Editorial Changed language and formatting in the technical content. 7/20/2007 2.0 Major Updated and revised the technical content. 8/10/2007 2.0.1 Editorial Changed language and formatting in the technical content. 9/28/2007 2.1 Minor Clarified the meaning of the technical content. 10/23/2007 3.0 Major Updated and revised the technical content. 11/30/2007 4.0 Major Updated and revised the technical content. 1/25/2008 5.0 Major Updated and revised the technical content. 3/14/2008 6.0 Major Updated and revised the technical content. 5/16/2008 7.0 Major Updated and revised the technical content. 6/20/2008 8.0 Major Updated and revised the technical content. 7/25/2008 8.1 Minor Clarified the meaning of the technical content. 8/29/2008 8.1.1 Editorial Changed language and formatting in the technical content. 10/24/2008 8.2 Minor Clarified the meaning of the technical content. 12/5/2008 8.3 Minor Added Windows 7 Applicability. 1/16/2009 8.3.1 Editorial Changed language and formatting in the technical content. 2/27/2009 8.4 Minor Clarified the meaning of the technical content. 4/10/2009 8.4.1 Editorial Changed language and formatting in the technical content. 5/22/2009 8.4.2 Editorial Changed language and formatting in the technical content. 7/2/2009 9.0 Major Updated and revised the technical content. 8/14/2009 9.0.1 Editorial Changed language and formatting in the technical content. 9/25/2009 9.1 Minor Clarified the meaning of the technical content. 11/6/2009 10.0 Major Updated and revised the technical content. 12/18/2009 11.0 Major Updated and revised the technical content. 1/29/2010 11.0.1 Editorial Changed language and formatting in the technical content. 3/12/2010 12.0 Major Updated and revised the technical content. 4/23/2010 12.0.1 Editorial Changed language and formatting in the technical content. 2 / 195 [MS-OAUT] - v20210625 OLE Automation Protocol Copyright © 2021 Microsoft Corporation Release: June 25, 2021 Revision Revision Date History Class Comments 6/4/2010 12.0.2 Editorial Changed language and formatting in the technical content. No changes to the meaning, language, or formatting of the 7/16/2010 12.0.2 None technical content. No changes to the meaning, language, or formatting of the 8/27/2010 12.0.2 None technical content. No changes to the meaning, language, or formatting of the 10/8/2010 12.0.2 None technical content. No changes to the meaning, language, or formatting of the 11/19/2010 12.0.2 None technical content. 1/7/2011 13.0 Major Updated and revised the technical content. No changes to the meaning, language, or formatting of the 2/11/2011 13.0 None technical content. No changes to the meaning, language, or formatting of the 3/25/2011 13.0 None technical content. No changes to the meaning, language, or formatting of the 5/6/2011 13.0 None technical content. 6/17/2011 13.1 Minor Clarified the meaning of the technical content. No changes to the meaning, language, or formatting of the 9/23/2011 13.1 None technical content. 12/16/2011 14.0 Major Updated and revised the technical content. No changes to the meaning, language, or formatting of the 3/30/2012 14.0 None technical content. No changes to the meaning, language, or formatting of the 7/12/2012 14.0 None technical content. No changes to the meaning, language, or formatting of the 10/25/2012 14.0 None technical content. No changes to the meaning, language, or formatting of the 1/31/2013 14.0 None technical content. 8/8/2013 15.0 Major Updated and revised the technical content. No changes to the meaning, language, or formatting of the 11/14/2013 15.0 None technical content. No changes to the meaning, language, or formatting of the 2/13/2014 15.0 None technical content. No changes to the meaning, language, or formatting of the 5/15/2014 15.0 None technical content. 6/30/2015 16.0 Major Significantly changed the technical content. No changes to the meaning, language, or formatting of the 10/16/2015 16.0 None technical content. No changes to the meaning, language, or formatting of the 7/14/2016 16.0 None technical content. 3 / 195 [MS-OAUT] - v20210625 OLE Automation Protocol Copyright © 2021 Microsoft Corporation Release: June 25, 2021 Revision Revision Date History Class Comments No changes to the meaning, language, or formatting of the 6/1/2017 16.0 None technical content. 9/15/2017 17.0 Major Significantly changed the technical content. 9/12/2018 18.0 Major Significantly changed the technical content. 4/7/2021 19.0 Major Significantly changed the technical content. 6/25/2021 20.0 Major Significantly changed the technical content. 4 / 195 [MS-OAUT] - v20210625 OLE Automation Protocol Copyright © 2021 Microsoft Corporation Release: June 25, 2021 Table of Contents 1 Introduction .......................................................................................................... 11 1.1 Glossary ......................................................................................................... 11 1.2 References ...................................................................................................... 14 1.2.1 Normative References ................................................................................. 14 1.2.2 Informative References ............................................................................... 14 1.3 Overview ........................................................................................................ 15 1.4 Relationship to Other Protocols .......................................................................... 18 1.5 Prerequisites/Preconditions ............................................................................... 18 1.6 Applicability Statement ..................................................................................... 18 1.7
Load more

Recommended publications
  • Interaction Designer COM API Reference Printed Help
    PureConnect® 2020 R1 Generated: 28-February-2020 Interaction Designer COM Content last updated: 09-January-2020 API Reference See Change Log for summary of changes. Printed Help Abstract This document contains Component Object Model (COM) Application Programming Interface (API) reference content for Interaction Designer. For the latest version of this document, see the PureConnect Documentation Library at: http://help.genesys.com/cic. For copyright and trademark information, see https://help.genesys.com/cic/desktop/copyright_and_trademark_information.htm. 1 Table of Contents Table of Contents 2 Introduction 13 The Component Object Model 13 Interface-based programming using objects 13 Objects exposed by Designer COM API 13 Other objects represent steps, links between steps, and tool step exit paths. 14 COM Interface Information 14 Naming Conventions in the Designer COM API Reference 15 About GUIDs, UUIDs, and CLSIDs 15 COM Clients and Servers 15 General Programming Tips 16 Interfaces 17 II3ID Interface 19 Overview 19 Methods 19 Properties 20 II3ID::CreateHandler Method 21 II3ID::CurrentHandler Method 22 II3ID::EscapeString Method 22 II3ID::GetErrorMessage Method 23 II3ID::GetLicenseInfo Method 23 II3ID::MessageBox Method 24 II3ID::OpenHandler Method 25 II3ID::QueryNativeTypeName Method 25 II3ID::ReadProfileLong Method 26 II3ID::ReadProfileString Method 27 II3ID::RegisterForIdEvents Method 28 II3ID::UnescapeString Method 28 II3ID::WriteProfileLong Method 29 II3ID::WriteProfileString Method 30 II3ID::CurrentHandlerSelectedSteps Property
    [Show full text]
  • Microsoft Patches Were Evaluated up to and Including CVE-2020-1587
    Honeywell Commercial Security 2700 Blankenbaker Pkwy, Suite 150 Louisville, KY 40299 Phone: 1-502-297-5700 Phone: 1-800-323-4576 Fax: 1-502-666-7021 https://www.security.honeywell.com The purpose of this document is to identify the patches that have been delivered by Microsoft® which have been tested against Pro-Watch. All the below listed patches have been tested against the current shipping version of Pro-Watch with no adverse effects being observed. Microsoft Patches were evaluated up to and including CVE-2020-1587. Patches not listed below are not applicable to a Pro-Watch system. 2020 – Microsoft® Patches Tested with Pro-Watch CVE-2020-1587 Windows Ancillary Function Driver for WinSock Elevation of Privilege Vulnerability CVE-2020-1584 Windows dnsrslvr.dll Elevation of Privilege Vulnerability CVE-2020-1579 Windows Function Discovery SSDP Provider Elevation of Privilege Vulnerability CVE-2020-1578 Windows Kernel Information Disclosure Vulnerability CVE-2020-1577 DirectWrite Information Disclosure Vulnerability CVE-2020-1570 Scripting Engine Memory Corruption Vulnerability CVE-2020-1569 Microsoft Edge Memory Corruption Vulnerability CVE-2020-1568 Microsoft Edge PDF Remote Code Execution Vulnerability CVE-2020-1567 MSHTML Engine Remote Code Execution Vulnerability CVE-2020-1566 Windows Kernel Elevation of Privilege Vulnerability CVE-2020-1565 Windows Elevation of Privilege Vulnerability CVE-2020-1564 Jet Database Engine Remote Code Execution Vulnerability CVE-2020-1562 Microsoft Graphics Components Remote Code Execution Vulnerability
    [Show full text]
  • 4. Simulation Software: Current
    4. SIMULATION SOFTWARE : CURRENT EXPERIENCES AND THE DOT NET SIM PROJECT Chapter overview 64 4.1. Current experiences in simulation software: 66 4.1.1. Process Simulator TM 67 4.1.2. Micro Saint Sharp TM 69 4.1.3. HighMast TM 71 4.2. An alternative vision for simulation software 73 4.3. The idea of DotNetSim 79 4.4. The DotNetSim computing technological background 81 4.4.1. The Microsoft Automation 81 4.4.2. The Microsoft .NET Framework 83 4.4.3. .NET Framework’s Architectural components 85 4.4.4. Multiplatform and multiple lingual integration 88 4.4.5. Integration of Microsoft Office with the .NET Framework 90 4.5. The DotNetSim prototype 91 4.5.1. DotNetSim and other developments 93 4.6. The Chapter in context 96 CHAPTER OVERVIEW The successive advances in computer science have constantly increased the 64 CHAPTER 4 - SIMULATION SOFTWARE : CURRENT EXPERIENCES AND THE DOT NET SIM expectations of the users and developers of application software, simulation software applications in our case. The early expectations and concerns with the proper processing of the input data were replaced by concerns over the portability, usability, extension and integration of software. Nowadays, correct functioning, portability and ease of use are taken for granted. It is also taken for granted that simulation packages are extensible to meet specific needs and that data can flow in and out of different packages. Current expectations and concerns are diverse, but focus mainly on the ease and speed of customisation. However, it is likely that, some time in the future, developers, builders or end users may want tools that let them select, modify and assemble only the functionality that each simulation solution requires.
    [Show full text]
  • The Microsoft Way: COM, OLE/Activex, COM+, and .NET CLR
    8557 Chapter 15 p329-380 8/10/02 12:24 pm Page 329 CHAPTER FIFTEEN The Microsoft way: COM, OLE/ActiveX, COM+, and .NET CLR In a sense, Microsoft is taking the easiest route. Instead of proposing a global standard and hoping to port its own systems to it, it continually re-engineers its existing application and platform base. Component technology is intro- duced gradually, gaining leverage from previous successes, such as the original Visual Basic controls (VBX – non-object-oriented components!), object link- ing and embedding (OLE), OLE database connectivity (ODBC), ActiveX, Microsoft Transaction Server (MTS), or active server pages (ASP). In the standards arena, Microsoft focuses mostly on internet (IETF) and web (W3C) standards. More recently, some of its .NET specifications (CLI and C#) where adopted by ECMA – a European standards body with a fast track to ISO (ECMA, 2001a, 2001b). Microsoft is not trying to align its approaches with OMG or Java standards. While Java figured prominently in Microsoft’s strategy for a while, it has been relegated to a mere continuation of support of its older Visual J++ product – in part as a result of a settlement between Sun and Microsoft. In addition, under the name Visual J# .NET, Microsoft offers a migration tool to .NET, primarily targeting users of Visual J++ 6.0. As part of the .NET initiative, Microsoft is promoting language neutrality as a major tenet of CLR and aims to establish a new language, C#. C# adopts many of the successful traits of Java, while adding several distinctive features of its own (such as value types) and not supporting key Java features (such as inner classes).
    [Show full text]
  • Open Excel Spreadsheet Using C
    Open Excel Spreadsheet Using C Assayable Jens dingo very discretionally while Anders remains itchiest and pitchier. Carlyle usually rainproofs psychically or syndicating appetizingly when indeterminate Herold buccaneers undutifully and sedately. Lily-white Lex bowse his placket disinherits pitapat. A Simple reward to Read on Excel Spreadsheet Let us start than opening form sample spreadsheet from openpyxl import loadworkbook. Never shot out touch the latest updates and handy tips for getting the most fell of Google Docs. Places the bitch in the worksheet header. Follow the options in effect from the compress function designed for the file extension is. Created in asp. While traveling outside, i keep it could be relied on this process to do this. The Google Sheets you friend with added security and overlap for teams. Excel evaluate the client machine. LibXL is enterprise library for whole reading precise writing the Excel files xlsxlsx without OLE automation and Microsoft Excel Supports C C CNET Delphi PHP. What excel spreadsheets using the use to us by opening a worksheet? The spreadsheet using a better in a good future of opening a string columns have used on which you need that we make the formula of. Curated by its Real Python team. SpreadsheetOpenCMyModelsSales Numbersxls ExcelWorkbook. Make it open spreadsheet using open excel spreadsheet as column headers and csv file which office access. This programming language has gained traction over recent years. How quite i like an excel file using C UNIX and Linux Forums. C code to update excel became The ASPNET Forums. There appear not be literally tens of thousands of them.
    [Show full text]
  • Object Oriented Programming
    A SYNOPSIS OF SOFTWARE TECHNOLOGIES USED IN TODAY’S ENGINEERING SOFTWARE Ashley Hull, Ph.D. Hasmet Genceli, Ph.D. Michael W. Hlavinka, Ph.D., P.E. Bryan Research & Engineering, Inc. P.O. Box 4747 Bryan, TX 77805 USA www.bre.com ABSTRACT Most engineers have little familiarity with the software technologies that provide the framework for the variety of applications they employ, from word processors to process simulators. While adequate for casual use of an application, a more thorough understanding of these technologies is required in order to extend an application and provide custom behavior. Usually the effort required to perform small customizations is not significant provided the framework is understood. This paper introduces Object-Oriented Programming (OOP), OLE Automation, and Extensible Markup Language (XML), three common technologies used in programs. A conceptual discussion of OOP is presented along with examples where the paradigm may be encountered. Automation is introduced with illustrations of how this feature can extend an application. Finally, XML is summarized along with a discussion of some of the tools and supporting technologies used with XML. The aim of this paper is to give a basic understanding of how and when these technologies can be exploited based on specific applications and tasks. A SYNOPSIS OF SOFTWARE TECHNOLOGIES USED IN TODAY’S ENGINEERING SOFTWARE INTRODUCTION Commercial software today is normally built upon several software technologies. These technologies provide a common framework that is consistent from one application to another. This framework is present in applications from word processors to process simulators. While an understanding of these technologies is not required for casual use of the application, some knowledge of this framework will be required to extend an application to provide custom behavior outside of the design of the vendor.
    [Show full text]
  • Using SAS® Data to Drive Microsoft Office Darren Key and David Shamlin, SAS Institute, Cary, NC
    NESUG 15 Emerging Technologies Using SAS® Data To Drive Microsoft Office Darren Key and David Shamlin, SAS Institute, Cary, NC Office applications expose groups of related features through ABSTRACT automation interfaces. An interface is a collection of functions (also called methods) and attributes (also called properties) that Microsoft Office provides tools for integrating its suite of can be called from other application code. In one of our case programs with other vendors’ data sources. There are a variety of studies, we use a special automation interface that allows Excel ways to do this using various ActiveX components and VBA and Access to call custom data import and export wizards scripting techniques. While the number of choices available can implemented as COM add-ins. The interface is called add to the complexity of creating a customized solution, the IDTExtensibility2 and contains five methods: basics of integrating with SAS data sources can be simplified with some basic code patterns for migrating data and reports between • Microsoft Office and SAS. OnAddInsUpdate • OnBeginShutdown We will outline basic patterns for importing SAS data into • OnConnection Microsoft Office documents as well as exporting data back to • OnDisconnetion SAS. The paper gives implementations of these patterns in the • OnStartupComplete form of Visual Basic code that can be customized for site-specific usage scenarios. We will demonstrate the application of these Each of these methods is called by the Office application (also techniques to tasks involving the migration of data between SAS called the host application) running the add-in during different data sets and Microsoft Office and Outlook applications.
    [Show full text]
  • (Forte 4GL) Integrating with External Systems, Version
    Integrating with External Systems Release 3.5 of Forte™ 4GL Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, CA 94303 U.S.A. 1-800-786-7638 Part No. 806-6672-01 October 2000, Revision A Copyright 2000 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, California 94303, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in this product. In particular, and without limitation, these intellectual property rights include U.S. Patent 5,457,797 and may include one or more additional patents or pending patent applications in the U.S. or other countries. This product is distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. c-tree Plus is licensed from, and is a trademark of, FairCom Corporation. Xprinter and HyperHelp Viewer are licensed from Bristol Technology, Inc. Regents of the University of California. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun Logo, Forte, and Forte Fusion are trademarks or registered trademarks of Sun Microsystems, Inc.
    [Show full text]
  • Intranet-Based Management of CAN Devices
    Intranet-Based Management of CAN Devices Dr.-Ing. Martin Wollschlaeger, Dipl.-Ing. Stefan Wehrmann With the steadily growing use of CAN devices within complex automation systems, the need for effective management solutions becomes more and more obvious. The spreading integration of CAN systems into Local Area Networks (LAN) provides the opportunity to build such solutions on intranet-based technologies like HTTP or COM/DCOM. Particularly the chances of a link between the intranet-stored information and the fieldbus layer let the development of a new generation of management tools be more than likely. Based on the illustration of principles for connecting fieldbus and LAN new concepts for the representation of CAN Higher Layer Protocol structures and data by intranet-based objects are introduced. Examples of practical realizations of the concepts for managing CAN modules prove the feasibility and show the prospects. 1. Introduction providing easy access to manufacturing related data from standard office One of the most outstanding trends in in- environment. This offers a starting point formation technology’s recent develop- for the implementation of management ments is the trend towards network-centric functions for the underlying fieldbus and its systems. Special attention has to be paid components, that are accessible from any to the overwhelming development of the point within the process information Internet and its enabling technologies in system. hard- and software, like TCP/IP, compo- nentware, browser technology, Java etc. 2. Integration concepts Using these technologies in an Intranet on There are different scenarios for the inte- top of a LAN enables the integration of gration of fieldbus systems into LANs different hard- and software platforms, as (Figure 1).
    [Show full text]
  • Developing ADO.NET and OLE DB Applications
    DB2 ® DB2 Version 9 for Linux, UNIX, and Windows Developing ADO.NET and OLE DB Applications SC10-4230-00 DB2 ® DB2 Version 9 for Linux, UNIX, and Windows Developing ADO.NET and OLE DB Applications SC10-4230-00 Before using this information and the product it supports, be sure to read the general information under Notices. Edition Notice This document contains proprietary information of IBM. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties, and any statements provided in this manual should not be interpreted as such. You can order IBM publications online or through your local IBM representative. v To order publications online, go to the IBM Publications Center at www.ibm.com/shop/publications/order v To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at www.ibm.com/ planetwide To order DB2 publications from DB2 Marketing and Sales in the United States or Canada, call 1-800-IBM-4YOU (426-4968). When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. ADO.NET development for .NET common language runtime (CLR) routines . .57 Supported .NET CLR routine development software 58 DB2 databases . .1 Support for external routine development in ADO.NET application development .
    [Show full text]
  • Microsoft Excel Demo
    Oracle COM Automation Developer’s Guide Release 8.1.6 for Windows NT January 2000 Part No. A73027-01 Oracle COM Automation Developer’s Guide, Release 8.1.6 for Windows NT Part No. A73027-01 Copyright © 1999, 2000 Oracle Corporation. All rights reserved. Contributors: Eric Belden, Kin Lau, Kian Fai Leong, Barmak Meftah, Steve Norall, Jeff Stein The Programs (which include both the software and documentation) contain proprietary information of Oracle Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation. If the Programs are delivered to the U.S. Government or anyone licensing or using the programs on behalf of the U.S. Government, the following notice is applicable: Restricted Rights Notice Programs delivered subject to the DOD FAR Supplement are "commercial computer software" and use, duplication, and disclosure of the Programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement.
    [Show full text]
  • Hyperion® System 9 BI + Interactive Reporting Object Model And
    HYPERION® SYSTEM™ 9 BI+™ INTERACTIVE REPORTING™ RELEASE 9.2 OBJECT MODEL AND DASHBOARD DEVELOPMENT SERVICES DEVELOPER’S GUIDE VOLUME I: DASHBOARD DESIGN GUIDE Copyright 1989-2006 Hyperion Solutions Corporation. All rights reserved. “Hyperion,” the Hyperion logo, and Hyperion’s product names are trademarks of Hyperion. References to other companies and their products use trademarks owned by the respective companies and are for reference purpose only. No portion hereof may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the recipient’s personal use, without the express written permission of Hyperion. The information contained herein is subject to change without notice. Hyperion shall not be liable for errors contained herein or consequential damages in connection with the furnishing, performance, or use hereof. Any Hyperion software described herein is licensed exclusively subject to the conditions set forth in the Hyperion license agreement. Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the applicable Hyperion license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (Oct 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14, as applicable. Hyperion Solutions Corporation 5450 Great America Parkway Santa Clara, California 95054 Printed in the U.S.A. Contents Preface . ix Audience . x Document Structure . x Related Documents . x Where to Find Documentation . xi Help Menu Commands . xi Conventions . xii Additional Support .
    [Show full text]