Making It Happen
Accounting and Information Technology Assistance and Support
Sage Custom Integration - Tables & Fields that are available.

Note that when using importing data a lot of the filed are not required as they are calculated on the fly according to the normal sage rules for data entry.

To identify the names of the various fields in the Sage 50 user interface for the report designer/ODBC see the table field finder unfortunately the ODBC/report designer variables do not always correspond with the field names in the tables, but they generally do.  If you need help ask.

In various place sage uses Status Codes and Values these are detailed here

Record numbers are generally used when updating existing data to select the transaction to update, they are not "Sage" fields but pseudo fields created to allow easy updating of records.

Pseudo tables are creates for the BOMS and Scheme Discounts to make importing easier, there are no exports for these, conversely Sage has dummy tables for doing things like BOM_COMPONENTS

Sample csv's and xmls are a straight dump of the demo data in headed csv and xml format respectively.

The powerful interpreter with the product is quite capable of extracting information from complex structures like printed invoices that have been saves as text files as well as data from a wide range of other source such as csv, headed csv, xml, MS access mdb, excel spreadsheets, any ODBC source, pipe delimited, emails, ftp server, web servers. We have even done strange mashups of pipe delimited embedded inside csv's!

Not all fields are available in all versions of Sage 50  things are always being added and occasionally changed.

In addition there are native data table structures that we can write custom dictionaries to access. tables\native\index.htm