opensynchelp

Recommendations

Info

OpenSync The database structure document - This PDF file is installed in the OpenSync installation folder The OpenSync Database Browser - This utilty provides an interactive way to browse the database tables and view the actual data contained in them. More information is located in the section named Database Browser Overview Schema - Overview Created with the Personal Edition of HelpNDoc: Full-featured EPub generator The topics in this seciton are meant to provide an introduction to characteristcs of the schema common to all database table. This includes: Table types Primary Keys Relationships Indexes Working with Items Custom Fields Adding Tables and Fields Report Tables Created with the Personal Edition of HelpNDoc: Easy to use tool to create HTML Help files and Help web sites Table Types Schema - Table Types There are five fundamental table types in the OpenSync schema. These are: List Tables List tables contain QuickBooks data entities (cusotmers, employees, other names and vendors), items, and other QuickBooks list elements. Transaction tables Transaction tables contain QuickBooks data for transactions such as invoices, bills, check, etc. Child Tables Child tables are always related to either a list or transaction table. The table name for child tables always ends with the word "detail". Examples of child tables include: InvoiceLinedetail, and ItemGroupLineDetail. System Tables System tables include the history and error_table and are used by OpenSync to track the table status and the status of QuickBooks updates respectively. Primary Keys Created with the Personal Edition of HelpNDoc: Easy CHM and documentation editor Schema - Overview 42 / 66
OpenSync Although the default schema does not define any primary keys, most tables do contain them. Here are the general rules regarding primary keys. List Tables ListID is the primary key. The FullName(where used) or Name field is also a unique key for these tables. Transaction tables TxnID is the primary key. Child Tables Child tables used in transactions contain a field named TxnLineID which is a primary key. Child tables without this field do not contain a primary key. System Tables System tables do not include a primary key. If desired, you can define these fields as primary keys to the database. Created with the Personal Edition of HelpNDoc: Full-featured multi-format Help generator Relationships Schema - Relationships There are two primary relationship type in the schema. Parent Child relationships These relationships link a parent table to one or more child tables. They can apply to both list and transaction tables. The format for these relationships is: Parent.ListID -> Child.IDKEY for list tables Parent.TxnID -> Child.IDKEY for transaction tables Reference relationships These relationships link list entries to other list or transaction tables. The format these links use is: TableNameRef_ListID TableNameRef_FullName TableName will indicate the table being referenced. For example, the column named CustomerRef_ListID refers to the ListID field in the customer table. For related tables that do not contain a FullName column, the Ref_FullName column will refer to the Name column in the target table. Adding Relationships Relationships defined within the database schema are not support to to referential integrity constraints. You should only define the relationships to be used within your queries. Indexes Created with the Personal Edition of HelpNDoc: Easily create EBooks 43 / 66
Page 1 and 2: OpenSync Copyright © 2013 by Syner
Page 3 and 4: OpenSync Updating QuickBooks ......
Page 5 and 6: OpenSync Starting OpenSync Add a Co
Page 7 and 8: OpenSync The OpenSync screen uses t
Page 9 and 10: OpenSync Select the location and na
Page 11 and 12: OpenSync On this screen, you should
Page 13 and 14: OpenSync Now you need to tell OpenS
Page 15 and 16: OpenSync Run a Task Run a Task Task
Page 17 and 18: OpenSync Task Status The task statu
Page 19 and 20: OpenSync If you are using the trial
Page 21 and 22: OpenSync Adding a company file Addi
Page 23 and 24: OpenSync To add a database for use
Page 25 and 26: OpenSync Oracle The final step in a
Page 27 and 28: OpenSync The database status screen
Page 29 and 30: OpenSync Refresh Report operations
Page 31 and 32: OpenSync The final step in adding a
Page 33 and 34: OpenSync Running a Task Tasks can b
Page 35 and 36: OpenSync Task Status The task statu
Page 37 and 38: OpenSync Information - Provides gen
Page 39 and 40: OpenSync The OpenSync background se
Page 41: OpenSync The browser screen consist
Page 45 and 46: OpenSync Custom field defeinitions
Page 47 and 48: OpenSync This status display indica
Page 49 and 50: OpenSync Fields included are: Err_N
Page 51 and 52: OpenSync Phone Contact OtherNameAdd
Page 53 and 54: OpenSync Supported Fields -ItemNonI
Page 55 and 56: OpenSync Processing Transactions Th
Page 57 and 58: OpenSync Amount Class ListID or Ful
Page 59 and 60: OpenSync Estimates Estimate Memo Pa
Page 61 and 62: OpenSync IDKEY (Required) - Links t
Page 63 and 64: OpenSync -SalesOrderLineDetail Tabl
Page 65 and 66: OpenSync Vendor ListID or FullName

opensynchelp

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?