1 White Paper Reporting and Data Access Methods Get the most flexibility in creating reports, lists or other documents Table of Contents
2 Sage ACT! Introduction... 3 Data Access Overview... 3 OLE DB Reporting Provider... 3 Sage ACT! Reader... 8 Sage ACT! Password Sage ACT! Software Developers Kit Conclusion Recommendations Data Access Method Comparison Terms and Concepts OLE DB v1.0 vs. v2.0 Comparison Reporting and Data Access Methods 2
3 Introduction The Sage ACT! application provides its own Report Writer that offers a number of stock Reports, Envelopes and Labels which allow users to produce a variety of reports and correspondence. These items are based upon templates which can be further modified or copied to create a customized and specific solution as needed. Template customization 1 is performed by the user right from within the application using the Sage ACT! Report Designer. In addition to Report Templates, the Sage ACT! architecture provides four additional Data Access Methods. These methods can be used for querying, reporting and data extraction: Sage ACT! OLE DB Reporting Provider Sage ACT! Reader Utility and account (Sage ACT! Premium only) Sage ACT! Password Utility (Sage ACT! Premium only) Sage ACT! SDK (Software Developers Kit) The objective of providing four additional Data Access methods is to offer the user the most flexibility in creating reports, lists or other documents. The objective of providing these additional methods outside of the Sage ACT! application is to offer the user the most flexibility in creating reports, lists or other documents to suit most any need. This includes data extraction to consolidated databases for rollup, as well as highly-customized reports using third-party software such as Crystal Reports. Data Access Overview While the Sage ACT! Report Designer offers a fairly comprehensive ability of creating custom reports and other correspondence, it can be limited in some aspects. Depending upon the task, data security may or may not be of concern. Such a case might include the need to perform unconstrained data rollups to a company or corporate level for consolidated reporting or other analytics. The four Data Access Methods each offer a very different approach and data exposure. Below is a discussion of each. OLE DB Reporting Provider The Sage ACT! OLE DB Reporting Provider is a data source provider written by Sage and is included with Sage ACT! Pro and Sage ACT! Premium (includes access via Windows and web). The Provider is designed to leverage the underlying client-server platform and the power of the Microsoft SQL Server relational database engine which services the Sage ACT! database. The Provider is the desired method for querying the Sage ACT! database both from within the application, as well as externally. There are two OLE DB Providers offered by Sage ACT!, referred to as version 1.0 and 2.0. Background and Specification: The version 1.0 Provider was created with the original development of ACT! by Sage 2005 (7.0). The primary objective and use-case is for external reporting of Sage ACT! data via third-party software such as Crystal Reports and Excel. The data returned is provided in a read-only manner and within the same security context as the Sage ACT! application, respecting both Record-Level Security (RLS) of the data and Field-Level Security (FLS) of the schema. 1 In Sage ACT! Premium (access via web), administrative functions must be performed on the Web server. The Provider is a communication library written in C++ that is essentially a pass-thru layer to communicate with the underlying SQL Server OLE DB data provider. The User provides an Sage ACT!.PAD file and user/password credentials for its connection/data source, then creates a physical connection to the database using a specific standard SQL Server login account. Reporting and Data Access Methods 3
4 The fundamental design approach of the OLE DB Provider is to expose Tables as database Views. These essentially look similar to database Tables, however, these Views contain relevant Sage ACT! implementation details such as Security and other rules. These Views are modeled in a buildingblocks approach, which actually differs somewhat between version 1.0 and version 2.0. With both versions, the Sage ACT! virtual columns (Address, and Phone) are flattened as the JOINS required to obtain those columns are already included in the base table View clause. These Views reside atop of underlying table Functions which contain the RLS and FLS security enforcements. The following highlights an example of the difference using the Contact and Note building-block records (Entities): Version 1.0: The Contact Notes View, named VRP_CONTACT_NOTE, contains all of the Note columns and just the Primary Key column for the Contact record (CONTACTID), not the Contact columns themselves. The User would need to JOIN the two Views appropriately to compose the query required to produce a report of Notes by Contact, for example. VRP_CONTACT TBL_CONTACT CONTACTID FIRSTNAME LASTNAME FULLNAME COMPANYNAME JOBTITLE CATEGORY USER1... Secured! TBL_ADDRESS LINE1... TBL_ ADDRESS TBL_PHONE PHONE... VRP_CONTACT_HISTORY VRP_CONTACT_NOTE TBL_CONTACT_HISTORY CONTACTID TBL_CONTACT_NOTE CONTACTID TBL_HISTORY HISTORYID DETAILS REGARDING START_DATE_TIME RECORD_MANAGER Secured! TBL_NOTE NOTEID NOTETEXT START_DATE_TIME RECORD_MANAGER Secured! Figure1 : This illustrates how the user needs to join the two views in Version 1.0. Version 2.0: The Contact Notes View, named CONTACT_NOTE, contains only the Primary Key columns of each Entity/Sub-Entity that you need to JOIN together. So this view will contain only two columns, the Note Primary Key column (NOTEID) and the Contact Primary Key column (CONTACTID). The User would need to JOIN this View to the three Entity Views (CONTACT, NOTE, CONTACT_NOTE) appropriately to compose the query required to produce a report of Notes by Contact, for example. Reporting and Data Access Methods 4
5 The version 2.0 Provider shipped with ACT! by Sage 2010 and Sage ACT! 2011 offers some additional capabilities and exposes metadata in different manner than the original Provider version 1.0. Figure 2 : This illustrates how the user needs to join the two views in Version 2.0. Figure 3: A more complete picture of the Sage ACT! Entity model, as implemented thru the OLE DB Provider version 2.0 Highlights of both OLE DB Provider versions include: Provides a read-only Sage ACT! logon to the database (using Sage ACT! credentials) Returns the same secured data, respecting both Record-Level and Field-Level Security, as the Sage ACT! application Provides a flattened data model presentation with relatively few View tables Dynamic by design updates automatically via Define Fields changes Connection is available with the Sage ACT! Framework SDK for third-party developer Add- Reporting and Data Access Methods It is recommended that 5 any new development or usage of the Sage
6 Ons Includes the ability to query Custom Table data (note: the Custom Tables feature is currently an SDK feature and not a core feature of the Sage ACT! application) The version 2.0 Provider shipped with ACT! by Sage 2010 and Sage ACT! 2011 offers some additional capabilities and exposes metadata in different manner than the original Provider version 1.0. It is recommended that any new development or usage of the Sage ACT! OLE DB Reporting Provider is done with the version 2.0 Provider, as support for the version 1.0 Provider may be discontinued in a subsequent release. Below are some highlighted differences of each version of the Provider: Version 1.0: The Views are constructed by a combination of using a static prefix ( VRP for View Reporting Provider) and the logical Table name. Any spillover tables, if applicable, generate their own Reporting View; it is the user s responsibility to correctly JOIN to these Views as necessary. Column names are fully-qualified for discoverability to include their table name and column name: <Tablename> <Columnname>. Column names are updated dynamically if they are renamed via the Define Fields task in Sage ACT!. There is no ability to query Activity data, nor Group or Company Contact Members. Extended data, such as Notes and History, is only accessible thru its parent Sage ACT! record of Contact, Group, Company or Opportunity (i.e. you cannot directly query Histories independent of its parent/associated record). Version 2.0: Separates Entity (i.e. Contact, Group, Company and Opportunity) and Sub-Entity (Note, History and Activity) records for better autonomy and easier, more flexible reporting. This allows more direct-reporting of Histories by User, for example, without regard to the type of Entity record the History is associated with. Views include all fields created as a result of record field customization (via Define Fields and/or any Add-On Products) one logical View per Entity or Sub-Entity. This provides a much simpler and centralized view of each record. Sage ACT! data type adherence for Uppercase, Lowercase and Initial Caps character fields. This means character data will appear just as it does in Sage ACT! Date, Time, and Datetime values default to local client time (configurable per connection). This means date/time values will appear as they do in Sage ACT!. A fully-expanded My Record View which includes all Contact fields. Optional descriptive text for Views and Columns (currently can only be set via the Sage ACT! SDK). This description can be seen in some third-party report tools, such as Crystal Reports, to assist the user in understanding what the View or column contains. With OLE DB v2.0, View column names are based on the field Alias Name which was introduced in ACT! by Sage This value can be set programmatically via the Sage ACT! SDK such as by an Add-On product; fields added via Define Fields are set with the name provided upon creation: Alias Names do not change; Queries will not break if field name changed Use the Database Structure>Fields Detail Report in ActDiag to see field name information ( OLE/DB Column is for the OLEDB v1.0 Provider, the OLEDB(2) Column shows the field Reporting and Data Access Methods 6
7 for the version 2.0 Provider) In addition to reporting software outside of the Sage ACT! application, ACT! by Sage 2010 and Sage ACT! 2011 include a Dashboard Component which uses the OLE DB Reporting Provider 2.0. This component, named Data Chart, can be customized to provide virtually any custom list or chart desired in a Dashboard. The source definition for this component is contained in the file Act.Dashboard.DataChart.XML which resides in the \Tools folder beneath where the Sage ACT! program is installed (by default c:\program Files\ACT\ACT for Windows). Upon installation, this file contains a number of stock queries which can be selected while in Design Layout mode. You can edit the XML file using any text editor, such as Notepad, to add, modify or delete a query. You may find it easiest to write the query first using a query or reporting tool, then copy & paste that SQL Server query into the XML file once you have what you want. The following depicts the Properties of creating a database connection via third-party reporting and query tools. As noted, there are two versions of the Sage ACT! Provider. Figure 4: This screen shot depicts the Propoerties of creating a database connection via third-party reporting and query tools. For the version 2.0 Provider, Additional connection options can be set on the Advanced tab of the connection properties dialog: Command Timeout Value (in seconds) in which the SQL Server query is allowed to complete before timing-out. Initialized to 30 seconds by default; if you experience Timeout expired messages, you can increase this value higher. A value of zero (0) specifies no timeout. Timezone Conversion Datetime values are stored in the Sage ACT! database as Universal Time (UTC). By default, the Provider will display these values using your Windows time zone setting. This can be changed, to view datetime values in another time zone. Reporting and Data Access Methods 7
8 The Sage ACT! Reader Utility only works with Sage ACT! Premium and Sage ACT! Premium (access via web). Figure 5: By default, the Provider will display datetime values using your Windows time zone setting. This can be changed to view another time zone. The Provider offers a good amount of abstraction and flattening of the relational tables which comprise a logical record in Sage ACT!. These records are referred to as Entities and Sub-entities which include: Contacts, Groups, Companies and Opportunities (Entities) Notes, Histories and Activities (Sub-entities) Custom sub-entity tables created via the Sage ACT! Software Developers Kit (SDK) Schema metadata Characteristic, Security and other supporting tables Typical Uses: Creating and running third-party reports such as Crystal Reports to return secured data (both record and field level) Reporting and querying data in Custom Tables (Sub-Entities) as this is currently not possible in the Sage ACT! Report Designer Custom Data Chart Dashboard Component queries within the Sage ACT! application In the Conclusion section of this document, there is a comparison table to facilitate the comparison of features/abilities between OLE DB version 1.0 and 2.0. Sage ACT! Reader The Sage ACT! Reader is a utility which is included with Sage ACT! Premium. This utility is used to set a password for the ACTREADER SQL Server account. This account has read-only access to all Premium databases on the machine for which the password has been set. The Sage ACT! Reader utility allows you: Establish a connection to the local Microsoft SQL Server (ACT7) instance to manage the instance ACTREADER password. Set (and reset) a password for the Sage ACT! Reader account. Once you set the password, you can use this account from any third-party software (for example, Crystal Reports or Microsoft Reporting and Data Access Methods 8
9 Access ), from virtually any machine, to connect to a Premium database on the machine and generate custom reports. Highlights include: Allows direct read-only SQL Server access to native tables and data Allows un-secured data access (i.e. no data is Private!) Does not require a Sage ACT! logon Supported in Sage ACT! Premium and Sage ACT! Premium (access via web) databases only Can be used for ODBC, OLE DB or SQL Server Native Client connections Requires fundamental SQL Server language and relational database knowledge to construct queries properly Sage ACT! Reader allows direct read-only SQL Server access to native tables and data. Typical Uses: Data extraction and rollup reporting, as no data is secured or filtered by security (no FLS nor RLS) To connect using ODBC connection when some reporting or query software does not support OLE DB, such as Microsoft Access. No data is Private! While the Sage ACT! Reader Utility itself only operates in a local context (on the local machine SQL Server instance in Sage ACT!), once the password has been set, access and logon to the SQL Server instance in Sage ACT! can be made from any machine which is able to communicate with the host database machine. The password can be changed at anytime later to change the password, however, the user must know the current password. If the current password has been forgotten, you must contact Sage ACT! Technical Support to guide you thru the process of resetting the ACT! Reader password. Figure 6: An example of the Sage ACT! Reader Utility. The following diagram depicts a machine running a SQL Server instance in Sage ACT!, hosting multiple Sage ACT! databases of both Premium and Pro Tier. As noted, the ActReader account will have access to any and all Premium Tier databases on the SQL Server instance, but no access to any Pro Tier databases. Reporting and Data Access Methods 9
10 Workstation Laptop Workstation ACT7 SQL Server Instance X Premium Standard DB1 DB2 DB3 The Sage ACT! Password Utility provides disclosure of the SQL Server sa password in Sage ACT!. Server Figure 7: This illustrates how the user needs to join the two views in Version 1.0. To use the ActReader account with a third-party reporting or query tool, you simply specify ACTREADER as the login name, then the password as it was set with the Sage ACT! Reader Utility. For the server, remember that Sage ACT! runs against a named instance of SQL Server, ACT7. You ll need to include this after your machine name, like: My_Machine\ACT7. You will find additional assistance in the Sage ACT! Help topic Using the Sage ACT! Reader utility. Sage ACT! Password The Sage ACT! Password is an optional utility which can be obtained from Sage ACT! Corporate Sales to view the per-machine SQL Server sa password. The sa account (meaning System Administrator) is a built-in account which is the utmost and most powerful account in the Microsoft SQL Server security model. Upon installation of Sage ACT!, the sa password is set to a random alpha-numeric value and is not disclosed to the end users or administrators. This is because much of the data integrity aspect of the application that drives the Sage ACT! platform resides in the database itself. This is done to maintain the highest degree of data integrity, performance, security and product quality. The sa account (meaning System Administrator) is a builtin account which is the utmost and most powerful account in the Microsoft SQL Server security model. It must be noted, however, that while the sa account has full read-write access to the Sage ACT! database and the SQL Server instance in Sage ACT!, directly modifying any configuration, definition, structure or data content is strictly prohibited by the Sage ACT! End User Licensing Agreement (EULA). To address these needs, Sage ACT! offers a very rich and comprehensive SDK for developers to accomplish such tasks (please see the following section for more information on the SDK). The three core reasons for the non-disclosure of the sa password includes: Application Integrity. The Sage ACT! SDK is built atop the database; a good degree of physical and business integrity is defined and maintained by code and logic that resides within the database. Un-securing the database exposing potential exploitations in both Sage ACT! procedural logic as well as the data. Data Security. The Sage ACT! security model is an important feature of the overall product. This can be defined by both our security features and rules designed into Sage ACT!, as well as the managed database files which are serviced by and only usable via SQL Server which employs its own security model. Protection of Intellectual Property. Un-securing the database exposing the physical implementation of both schema design and procedural code. It is for the same reason that Reporting and Data Access Methods 10
11 we do not publish our underlying SDK source code. The SDK is built upon the Microsoft.Net platform offering a highlycustomizable and featurerich programmatic environment for the developer. Figure 8: A screenshot of the Sage ACT! Password Utility (prior to clicking the Show button). Highlights of the Sage ACT! Password Utility include: Full read/write access to the SQL Server instance in Sage ACT! (although data and programmatic changes are strictly prohibited!) Highest level of SQL Server instance access Does not allow user to change/set their own sa password Full access to all databases, data, procedural objects and all other content Not supported for writing to and/or altering the SQL Server instance or databases (EULA violation) The Sage ACT! application itself is written to use the Sage ACT! SDK. Typical Uses: Third-party administration software such as online backup of SQL Server databases Security configuration when employing a clustered SQL Server configuration It is recommended that you review the other data access options reviewed in this document prior to pursuing the Sage ACT! Password Utility. Depending upon your requirement, usage of the sa account may either violate the Sage ACT! EULA or not provide the level and type of data access you are expecting. In many cases, usage of this account can be overkill. Sage ACT! Software Developers Kit The Sage ACT! SDK, or Software Developers Kit, is the preferred and supported method of interacting with the product and database for the purposes of writing data, as well as extending the Sage ACT! product itself. The SDK is built upon the Microsoft.Net platform offering a highly-customizable and feature-rich programmatic environment for the developer. In fact, the Sage ACT! application itself is written upon this platform, that is to say it uses this same Sage ACT! SDK. The Sage ACT! SDK consists of feature rich components that are highly extensible. Where Sage ACT! seeks to empower the end users to customize the product to their business, the Sage ACT! SDK helps third parties and other developers extend that vision through independent development. Highlights include: Developer-oriented approach requiring familiarity with programming concepts Requires a Sage ACT! logon Not Report Writer-friendly (i.e. Crystal Reports) Exposes built-in functionality for creating custom solutions Provides the Sage ACT! data experience Reporting and Data Access Methods 11
12 Reporting and Data Access Methods 12
13 Typical Uses: To further extend and customize the Sage ACT! application to meet a specific requirement by the user The Sage ACT! platform has three logical tiers: Application Framework Database Figure 9: This figure shows the SDK development platform. Conclusion The Sage ACT! product, supplemented by the four Data Access Methods described here, provides a robust, flexible and rich set of abilities to meet most all user reporting and data extraction needs. Sage ACT! offers users read-only access through two versions of the OLE DB Provider. Administrators can choose to set a password through Sage ACT! Reader to grant direct read-only access to all Premium databases. A higher level of security can be gained by using Sage ACT! Password which offers the most powerful account in the SQL Security model and provides full access to all databases. If an organization is seeking to customize Sage ACT! to its business, the SDK provides feature rich components that are highly extensible. The SDK is the preferred and supported method of writing data to Sage ACT!. Recommendations This document has provided a description of four different Reporting and Data Access Methods, capturing some highlights and abilities of each. Below is a table with some features and scenarios which may provide some guidance on selecting the most appropriate method to query the Sage ACT! data: Reporting and Data Access Methods 13
14 Data Access Method Comparison Characteristic / Requirement OLE DB v1.0 OLE DB v2.0 Sage ACT! Reader Sage ACT! Password Sage ACT! Product Tier: Sage ACT! Pro Sage ACT! Premium (including Sage ACT! Premium (access via web)) Respects Sage ACT! Security (FLS/ RLS) Objects Accessed Views Views Tables All Objects Column Naming convention Friendly Name as input by the user; changes when renamed System Alias Name; does not change when renamed in Define Fields Native physical name in SQL Server Native physical name in SQL Server Entities and Sub-entities available: Activities Group and Company Members Custom Tables (Sub-entities) available Spill-over table exposure View for each Spill-over table Spill-over tables included in Entity View Each physical table Each physical table Date/Time values UTC/GMT Local UTC/GMT UTC/GMT Sage ACT! character data type conformance OLE DB Connection ODBC Connection requirement Reporting and Data Access Methods 14
15 Terms and Concepts For the purposes of these Data Access Methods, the following series of terms will help you in understanding some of the challenges, and terminologies, often required when working with relational databases. Some terms are more specific to Sage ACT!, however. Base Table the core/primary table containing the stock and some custom (user-added) fields. There is one per Sage ACT! Entity (i.e. Record Type). Spillover Table table which extends a Sage ACT! Entity (such as Contact) beyond a physical table storage limitation by the underlying RDBMS. In SQL Server, as well as most other RDBMS vendor products, there are limitations in table size definition and the number of fields. Figure 10: A conceptual view of the Spillover Table design. Spillover tables are implemented as a one-to-zero-or-one cardinality (aka Z-cardinality), so there is not a one-for-one record in each Spillover table for each base table record. Only records on which one or more fields residing on that Spillover table will contain a record. Spillover tables inherit the Primary Key column (such as CONTACTID) of the Entity base table which they are extending. Access Control List (ACL) a list on each Sage ACT! Entity identifying the Users and/or Teams which have access to the record. Having access to a record does not imply nor infer action(s) that can be taken against that record that resides in the Sage ACT! Permissions module. Row-Level Security (RLS) only allow the requestor to see records to which they have access. For Entity records, this access is either direct (user themselves) or indirect (via Team membership) via ACL. For Sub-entities (Notes, Histories, Activities and custom Subentities) this means Private to the requesting User, or Public. Field-Level Security (FLS) only allow the requestor to see the contents/data of a field to which they have not beendenied access. This applies for all records in the table, it is not on Reporting and Data Access Methods 15
16 a record-by-record basis. Globally Unique Identifier (GUID) a 36-character alpha-numeric value used on most every table in the Sage ACT! database. Used as the Primary Key (identifier) for a record. Primary Key (PK) one, or more, field(s) on a table which is used to uniquely identify a record. No two records in the table can have the same Primary Key column value(s). Foreign Key (FK) a field on a dependent table (aka child table) that points to (references) a record in another table (aka parent table). A JOIN is generally performed between two tables using this Primary Key and Foreign Key relationship. Cardinality a mathematic phrase to express the number of records between two tables in a set (relation). For example, one record in the Contact table having three related records in the Address table has a 1:3, also referred to as a one-to-many, cardinality. Reporting and Data Access Methods 16
17 OLE DB v1.0 vs. v2.0 Comparison Feature / Behavior OLE DB v1.0 OLE DB v2.0 View Name View Structure Building Block Design Three Major Subject Areas My Record Sage ACT! Character Datatypes VRP_ prefixed Entity or Table Name based Each spillover table has its own View User has to determine which View a desired field resides on Complexity in INNER/OUTER JOIN logic for query writing Views are Entity-based Must query thru Entity to get to Subentity records (i.e. VRP_CONTACT_HISTORY) Must UNION all three History Views (Contact, Group, Company) to obtain all possible records Content (Contacts, Histories, etc.) Limited Configuration (Picklist, Team, User, etc.) Tables and Columns Shows limited fields Have to JOIN to VRP_CONTACT to get the My Record (Contact) fields Character datatypes are not rendered accordingly No prefix Entity and Subentity Name based Entity View will contain all fields including those on spillover tables Mitigates requirement to know where field resides JOIN complexity is eliminated Views are more autonomous Subentities have their own Views (i.e. HISTORY) Can query History independent of related Entity(ies) (no UNION req d) Relationship Views are now just Join Keys Content (Contacts, Histories, etc.) Configuration (Picklist, Team, User, History Types, Activity Types, etc.) Tables, Columns, Db Configuration, Primary and Foreign Keys Mirrors the CONTACT View no need to JOIN to CONTACT Also includes USERID Character datatypes are properly rendered Uppercase Lowercase Initial Caps Sage ACT! Date/Time Fields Expanded Stock Yes/No Fields Query Command Timeout Descriptions Displayed in UTC value Supports timezone conversion Displayed in Local Time Configuration per-connection on the Advanced tab Only the 0 or 1 values are available The 0 or 1 value is available A complementary character field is also available (localized to Yes No ) 0/1 recommended for WHERE clause Yes / No recommended for SELECT clause Non-configurable at 30 seconds Defaults to 30 seconds Configurable (Advanced tab) No Descriptions at any level Description available for: o Entity (View) o Column Note: Descriptions currently only settable via SDK Reporting and Data Access Methods 17
18 ASIA 210 Middle Road #06-04 IOI Plaza Singapore AUSTRALIA / NEW ZEALAND Level 6, 67 Albert Street Chatswood, NSW 2067 Australia BELGIUM / LUXEMBOURG Rue Natalis Liège Belgium CHINA Suite 2605, Liu Lin Tower No. 1 Huaihai Zhong Road Shanghai People s Republic of China FRANCE Ciel Service Commercial Sage ACT! 35, rue de la Gare Paris cedex 19 France GERMANY Emil-von-Behring Str Frankfurt am Main Germany INDIA 100, Second Floor Okhla Industrial Estate Phase-III New Delhi India IRELAND 3096 Lake Park Drive Citywest Business Park Dublin 24 Ireland +353 (0) MIDDLE EAST Office No. 315, Building 12 P O Box Dubai Internet City Dubai United Arab Emirates +971 (4) POLAND Sage sp. z o.o. Ul. Berna Warszawa Poland SOUTH AFRICA Softline Technology Park 102 Western Services Road Gallo Manor Ext 6 Johannesburg, 2191 South Africa SPAIN Labastida, Madrid España SWITZERLAND Sage Schweiz AG D4 Platz Root Langenbold Switzerland UNITED KINGDOM North Park Newcastle Upon Tyne NE13 9AA UNITED STATES 8800 North Gainey Center Drive Suite 200 Scottsdale, Arizona About Sage ACT! Sage ACT! makes it easy for you to have meaningful conversations with customers by giving you an organized view of the people you do business with. Like the millions of small businesses and sales teams who use Sage ACT!, you ll always be prepared with recent s, meeting notes, task reminders, and social media profiles, because all of these details live in one place. Important Note: Review Sage ACT! system requirements at You must purchase one license of Sage ACT! per user. Scalability varies based on hardware, size, and usage of your database. Compatibility: Visit or contact your add-on product provider to help determine compatibility. Due to new functionality available in ACT! by Sage 2010, we strongly recommend contacting your add-on product provider to confirm compatibility. Using versions of the add-on product that have not been confirmed compatible by the vendor may result in features behaving differently or not appearing within ACT! by Sage Sage Software, Inc. All rights reserved. Sage, the Sage logos, ACT!, and the Sage product and service names mentioned herein are registered trademarks or trademarks of Sage Software, Inc., or its affiliated entities. Business Objects and the Business Objects logo, Business Objects and Crystal Reports are the trademarks or registered trademarks of SAP France in the United States and/or other countries. Microsoft, SQL Server, Windows, Windows Vista, and the Windows logo are trademarks or registered trademarks of the Microsoft group of companies.. All other trademarks are the property of their respective owners. Sage 8800 N. Gainey Center Dr., Suite 200 Scottsdale, AZ
Reporting and Data Access Methods Get the most flexibility in creating reports, lists, or other documents Table of Contents Introduction... 1 Data Access Overview... 1 OLE DB Reporting Provider... 2 Background
Whitepaper Reporting and Data Access Methods ACT! by Sage Product Family Table of Contents Introduction... 3 Data Access Overview... 3 OLE DB Reporting Provider... 3 ACT! Reader... 8 ACT! Password... 10
White Paper Scalability Results Select the hardware configuration that s right for your organization to optimize performance Table of Contents Introduction... 3 Scalability... 3 Definition... 3 CPU and
White Paper Feeding Sales Find targeted leads with Sage Business Info Services for ACT!, powered by Hoover s. Table of Contents The challenge: Find relevant, yet cost-effective sales leads... 3 An easy
White Paper Microsoft Office Integration Achieve Greater Efficiencies When Using Both Sage ACT! and Office Tools in Daily Business Operations Sage ACT! Table of Contents Introduction... 3 Sage ACT! Integration
Make contact. Build relationships. Get results. Greg Miller General Manager and Partner Charter Capital ACT! User Since August 2000 Choose the #1 Selling Contact and Customer Manager Grow your business
Keys to a Successful ACT! by Sage Deployment Table of Contents Executive Summary...3 Deployment Scenarios...3. Deploying ACT! with a Local Database...3. Deploying ACT! Premium with a Shared Database...4.
White Paper ACT! by Sage 2010: Delivering on Usability and Productivity Easier than ever to learn, use, and do more! Table of Contents Executive Summary... 3 Introduction... 4 Proving Usability and Productivity...
White Paper Your Guide to Email Marketing A cost effective way to reach your customers and prospects Table of Contents Introduction... 3 Part One:... 3 Permission-based Email Marketing... 3 Part Two:...
grow your business with Sage SalesLogix Acquire Retain Develop Overview Sage SalesLogix, an award-winning Customer Relationship Management (CRM) solution, provides a complete view of customer interactions
White Paper Sage ACT! maximizes flexibility and provides options for securing data Table of Contents Introduction... 4 Sage ACT! Security Overview... 4 User Roles... 4 Types of Security in Sage ACT!...
White Paper Page 1 Table of Contents Introduction... 4 Architecture Overview... 4 Database Layer... 4 The Business Logic Layer... 5 Presentation Layer... 6 Premium (access via web) and AJAX... 7 What is
Authoring for System Center 2012 Operations Manager Microsoft Corporation Published: November 1, 2013 Authors Byron Ricks Applies To System Center 2012 Operations Manager System Center 2012 Service Pack
ACT! by Sage Premium for Workgroups 2007 (9.0) Administrator s Guide to the ACT! Reader Utility ACT! by Sage Premium for Workgroups 2007 (9.0) Administrator s Guide to the ACT! Reader Utility Copyright
INTRODUCTION: You can extract data (i.e. the total cost report) directly from the Truck Tracker SQL Server database by using a 3 rd party data tools such as Excel or Crystal Reports. Basically any software
Sage Intelligence Financial Reporting for Sage ERP X3 Installation Guide Revision 1.0. The software described in this document is protected by copyright, And may not be copied on any medium except as specifically
A- Z Glossary of CRM and Related Terms Application Programming Interface (API): A source code interface that a computer system or program library provides to support requests for services made via a computer
Sage 100 ERP Installation and System Administrator s Guide This is a publication of Sage Software, Inc. Version 2014 Copyright 2013 Sage Software, Inc. All rights reserved. Sage, the Sage logos, and the
Microsoft Dynamics Connector for Microsoft Dynamics Configuration Guide for Microsoft Dynamics SL Revised August, 2012 Find updates to this documentation at the following location: http://www.microsoft.com/download/en/details.aspx?id=10381
Benefits of Sage SalesLogix Visual Analyzer In-Memory Analysis over OLAP and Static Reporting Solutions Table of Contents The Emergence of a New Business Intelligence Space...3 Sage SalesLogix Visual Analyzer...3
Whitepaper Synchronization Architecture ACT! by Sage Product Family Table of Contents Introduction... 3 ACT! Synchronization Overview... 3 Goals and Objectives of the ACT! Synchronization Model... 4 Methods
: The Only Way to True 360 Customer Visibility and Seamless Data Consistency Table of Contents Executive Summary...3 Introduction...3 Customer Management and Business Process Challenges...3 Fundamentals
Vermont Oxford Network enicq 5 Documentation enicq 5 System Administrator s Guide Release 2.0 Published November 2014 2014 Vermont Oxford Network. All Rights Reserved. enicq 5 System Administrator s Guide
FileMaker 12 ODBC and JDBC Guide 2004 2012 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker and Bento are trademarks of FileMaker, Inc.
Act! Synchronization Understanding Act! Synchronization Table of Contents Introduction... 1 Synchronization Architecture... 1 Methods of Synchronizing... 1 What Is Synchronized... 4 Features and Capabilities
for Sage 100 ERP Business Insights Document 2012 Sage Software, Inc. All rights reserved. Sage Software, Sage Software logos, and the Sage Software product and service names mentioned herein are registered
TIBCO Spotfire Metrics Modeler User s Guide Software Release 6.0 November 2013 Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE
StruxureWare Power Monitoring 7.0.1 Installation Guide 7EN02-0308-01 07/2012 Contents Safety information 5 Introduction 7 Summary of topics in this guide 7 Supported operating systems and SQL Server editions
Data Access Guide BusinessObjects 11 Windows and UNIX 1 Copyright Trademarks Use restrictions Patents Copyright 2004 Business Objects. All rights reserved. If you find any problems with this documentation,
How to Prepare for the Upgrade to Microsoft Dynamics CRM 2013 (On-premises) COMPANY: Microsoft Corporation RELEASED: September 2013 VERSION: 1.0 Copyright This document is provided "as-is". Information
RFID Tracking System Installation Installation Guide Version 3.x 3M Track and Trace Solutions 3M Center, Building 225-4N-14 St. Paul, Minnesota 55144-1000 78-8123-9919-0, Rev. E 2003-2009, 3M. All rights
FAS Asset Accounting FAS CIP Accounting FAS Asset Inventory SQL Server Installation & Administration Guide Version 2011.1 2011 Sage Software, Inc. All rights reserved. Published by Sage 2325 Dulles Corner
SQL Server An Overview SQL Server Microsoft SQL Server is designed to work effectively in a number of environments: As a two-tier or multi-tier client/server database system As a desktop database system
Oracle Fusion Middleware Getting Started with Oracle Business Intelligence Publisher 11g Release 1 (11.1.1) E28374-02 September 2013 Welcome to Getting Started with Oracle Business Intelligence Publisher.
Getting Started Guide SAGE ACCPAC INTELLIGENCE Table of Contents Introduction... 1 What is Sage Accpac Intelligence?... 1 What are the benefits of using Sage Accpac Intelligence?... 1 System Requirements...
Sage Estimating (SQL) (formerly Sage Timberline Estimating) Release Notes Version 15.11 This is a publication of Sage Software, Inc. Copyright 2015. Sage Software, Inc. All rights reserved. Sage, the Sage
FileMaker 11 ODBC and JDBC Guide 2004 2010 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker is a trademark of FileMaker, Inc. registered
Interworks Interworks Cloud Platform Installation Guide Published: March, 2014 This document contains information proprietary to Interworks and its receipt or possession does not convey any rights to reproduce,
Author: Ryan J Adams Overview We will cover what Policy Based Management is and how you can leverage its power to better manage your environment. With PBM we'll see what it can and cannot do to help you
Profile synchronization guide for Microsoft SharePoint Server 2010 Microsoft Corporation Published: August 2011 Author: Microsoft Office System and Servers Team (email@example.com) Abstract This book
Sage 300 Construction and Real Estate Sage SQL Gateway with Executive Dashboard Installation and Reference Guide This is a publication of Sage Software, Inc. Copyright 2015 Sage Software, Inc. All rights
AD RMS Step-by-Step Guide Microsoft Corporation Published: March 2008 Author: Brian Lich Editor: Carolyn Eller Abstract This step-by-step guide provides instructions for setting up a test environment to
Sage 300 ERP 2014 What's New This is a publication of Sage Software, Inc. Copyright 2013. Sage Software, Inc. All rights reserved. Sage, the Sage logos, and the Sage product and service names mentioned
BusinessObjects Enterprise XI Release 2 Administrator s Guide BusinessObjects Enterprise XI Release 2 1 Patents Trademarks Copyright Third-party contributors Business Objects owns the following U.S. patents,
Polar Help Desk Installation Guide Copyright (legal information) Copyright Polar 1995-2005. All rights reserved. The information contained in this document is proprietary to Polar and may not be used or
Microsoft Terminal Server and Citrix Presentation Server Deployment Environments Understanding the use of Act! in a Terminal Server or Citrix Presentation Server environment Table of Contents Introduction...
GP Reports Viewer Dynamics GP Reporting Made Easy GP REPORTS VIEWER USER GUIDE For Dynamics GP Version 2015 (Build 5) Dynamics GP Version 2013 (Build 14) Dynamics GP Version 2010 (Build 65) Last updated
MBAM Self-Help Portals Authoring a self-help portal workflow for BitLocker Recovery Using Microsoft BitLocker Administration and Monitoring (MBAM) Technical White Paper Published: September 2011 Priyaa
Work Smart by Microsoft IT What s new in Access 2013 Customization note: This document contains guidance and/or step-by-step installation instructions that can be reused, customized, or deleted entirely
Converting to the Inmagic DB/Text for SQL Platform Copyright 2007 2011 by Inmagic (a subsidiary of SydneyPLUS International Library Systems). All rights reserved. Inmagic, the Inmagic logo, DB/Text, DB/TextWorks,
Micromedia International Technical study Author: Pierre Chevrier Number of pages: 17 Company: Micromedia International Date: 24/08/2011 Réf. : ETT_20110624_000001.docx Connecting to SQL server This document
Step-by-Step Guide to Securing Windows XP Professional with Service Pack 2 in Small and Medium Businesses 2004 Microsoft Corporation. All rights reserved. This document is for informational purposes only.
Frequently Asked Questions Sage Pastel Intelligence Reporting The software described in this document is protected by copyright, and may not be copied on any medium except as specifically authorized in
The Recipe for Sarbanes-Oxley Compliance using Microsoft s SharePoint 2010 platform Technical Discussion David Churchill CEO DraftPoint Inc. The information contained in this document represents the current
Active Directory Change Notifier Quick Start Guide Software version 3.0 Mar 2014 Copyright 2014 CionSystems Inc., All Rights Reserved Page 1 2014 CionSystems Inc. ALL RIGHTS RESERVED. This guide may not
Sage ERP MAS Everything you want to know about Sage ERP MAS Intelligence What is Sage ERP MAS Intelligence? Sage ERP MAS Intelligence (or Intelligence) empowers managers to quickly and easily obtain operations
Business Intelligence Getting Started Guide 2013 Table of Contents Introduction... 1 Introduction... 1 What is Sage Business Intelligence?... 1 System Requirements... 2 Recommended System Requirements...
Installation & Configuration Guide Bluebeam Studio Enterprise ( Software ) 2014 Bluebeam Software, Inc. All Rights Reserved. Patents Pending in the U.S. and/or other countries. Bluebeam and Revu are trademarks
Mobility Services Platform 3.1.1 Software Installation Guide Mobility Services Platform 3.1.1 Software Installation Guide 72E-100159-04 Revision D January 2008 2007 by Motorola, Inc. All rights reserved.
BusinessObjects Extended Analytics Architecture and recommendations BusinessObjects Extended Analytics FPM 7.0 Copyright Third-party contributors Copyright 2008 Business Objects. All rights reserved. Business
Software License Renewal Instructions SAS 9.3 Foundation for Microsoft Windows Note: In this document, references to Microsoft Windows or Windows include Microsoft Windows for x64. SAS software is licensed
Accessing Your Database with JMP 10 JMP Discovery Conference 2012 Brian Corcoran SAS Institute JMP provides a variety of mechanisms for interfacing to other products and getting data into JMP. The connection
Silect MP Author for Microsoft System Center Operations Manager Silect Software s MP Author User Guide September 2, 2015 Disclaimer The information in this document is furnished for informational use only,
Aras Innovator Authentication Setup Aras Innovator 9.1 Document #: 9.1.009032008 Last Modified: 3/12/2009 Copyright 2009 Aras Corporation ARAS CORPORATION Copyright 2009 All rights reserved Aras Corporation
TAC Vista TAC Pangaea WorkStation Vista FM Installation Manual TAC Vista Vista FM Installation Manual Copyright 2006-2010 Schneider Electric Buildings AB. All rights reserved. This document, as well as
Release Notes for Websense Email Security v7.2 Websense Email Security version 7.2 is a feature release that includes support for Windows Server 2008 as well as support for Microsoft SQL Server 2008. Version
SAP BusinessObjects Business Intelligence Suite Document Version: 4.1 Support Package 3-2014-05-07 Table of Contents 1 Document History....3 2 Introduction....4 2.1 About this Document....4 2.1.1 Constraints....4
Jet Data Manager 2012 User Guide Welcome This documentation provides descriptions of the concepts and features of the Jet Data Manager and how to use with them. With the Jet Data Manager you can transform
AlienVault Unified Security Management (USM) 4.x-5.x User Management Guide USM v4.x-5.x User Management Guide, rev 1 Copyright 2015 AlienVault, Inc. All rights reserved. The AlienVault Logo, AlienVault,
Overview of Active Directory Rights Management Services with Windows Server 2008 R2 Student Manual Module 3: Active Directory Rights Management Clients and Information Rights Management on Desktop Applications
www.novell.com/documentation Server Installation ZENworks Mobile Management 2.7.x August 2013 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of this
SDL Tridion R5 Content Management Implementation Guide 5.3 SP1 Read this document to implement and learn about the following Content Manager features: Publications Blueprint Publication structure Users
2014 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement.
Administration Guide for the System Center Cloud Services Process Pack Microsoft Corporation Published: May 7, 2012 Author Kathy Vinatieri Applies To System Center Cloud Services Process Pack This document
Orientation Course - Lab Manual Using the Virtual Managed Workplace site for the lab exercises Your instructor will provide the following information before the first lab exercise begins: Your numerical
Installation ***Important: It is highly recommended that you first take a backup of your current CRM Application Ribbons prior to importing this solution. Please do so by navigating to Settings > Solutions
Licensing the Corporate Modeler Suite Corporate Modeler Contents 02 Register the Corporate Modeler Suite and get a license key 03 What type of license do I need? 04 Register a client license for the Corporate
Why? Why? Table of Contents The 01 02 Why? 03 Some quotes from Paul Greenberg s Gets Wise blog 04 05 Quotes from ACT! clients 06 07 Quotes from clients 08 09 Quotes from clients 10 11 12 Why? 01 The At,
FileMaker 13 ODBC and JDBC Guide 2004 2013 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker and Bento are trademarks of FileMaker, Inc.