KB All Products
Which Office Connector module should I use to send data from Excel to Sage 300 CRE?
Click an application title below (e.g., "Accounts Payable") to view a list of the tables that you can send data to from Excel via Office Connector. Click on a specific table (e.g., "AP Invoice") to see which Office Connector modules can be used to create and/or update records. Refer to […]Common issues with custom reports after upgrading from Sage 100 Contractor v19 to v20
Background The upgrade from Sage 100 Contractor v19 to v20 represents a major change to the underlying database. Beginning with v20, Sage 100 Contractor now uses a Microsoft SQL Server database. Because of this, the database driver (which provides the connectivity between Liberty Reports and your Sage 100 Contractor data) […]Some PivotTables change after upgrading from Sage 100 Contractor v19 to v20
Background The upgrade from Sage 100 Contractor v19 to v20 represents a major change to the underlying database. Beginning with v20, Sage 100 Contractor now uses a Microsoft SQL Server database. Because of this, the database driver (which provides the connectivity between Liberty Reports and your Sage 100 Contractor data) […]Queries may not return correct results when conditioning on a nullable column after upgrading from Sage 100 Contractor v19 to v20
Background The upgrade from Sage 100 Contractor v19 to v20 represents a major change to the underlying database. Beginning with v20, Sage 100 Contractor now uses a Microsoft SQL Server database. Because of this, the database driver (which provides the connectivity between Liberty Reports and your Sage 100 Contractor data) […]Queries having parameters in the SELECT list fail after upgrading from Sage 100 Contractor v19 to v20
Background The upgrade from Sage 100 Contractor v19 to v20 represents a major change to the underlying database. Beginning with v20, Sage 100 Contractor now uses a Microsoft SQL Server database. Because of this, the database driver (which provides the connectivity between Liberty Reports and your Sage 100 Contractor data) […]Union queries containing parameters fail after upgrading from Sage 100 Contractor v19 to v20
Background The upgrade from Sage 100 Contractor v19 to v20 represents a major change to the underlying database. Beginning with v20, Sage 100 Contractor now uses a Microsoft SQL Server database. Because of this, the database driver (which provides the connectivity between Liberty Reports and your Sage 100 Contractor data) […]Queries with clauses in non-standard sequence fail after upgrading from Sage 100 Contractor v19 to v20
Background The upgrade from Sage 100 Contractor v19 to v20 represents a major change to the underlying database. Beginning with v20, Sage 100 Contractor now uses a Microsoft SQL Server database. Because of this, the database driver (which provides the connectivity between Liberty Reports and your Sage 100 Contractor data) […]Some GROUP BY queries fail after upgrading from Sage 100 Contractor v19 to v20
Background The upgrade from Sage 100 Contractor v19 to v20 represents a major change to the underlying database. Beginning with v20, Sage 100 Contractor now uses a Microsoft SQL Server database. Because of this, the database driver (which provides the connectivity between Liberty Reports and your Sage 100 Contractor data) […]Some SELECT DISTINCT queries fail after upgrading from Sage 100 Contractor v19 to v20
Background The upgrade from Sage 100 Contractor v19 to v20 represents a major change to the underlying database. Beginning with v20, Sage 100 Contractor now uses a Microsoft SQL Server database. Because of this, the database driver (which provides the connectivity between Liberty Reports and your Sage 100 Contractor data) […]