• Using SQL queries in a calculated field (report writer)

    Hello - I am struggling with the report writer and need some clarification (a long shot, since there is almost 0 documentation on the subject). I am proficient in T-SQL, so am confident in my ability to write queries, but can't get something very simple…
  • Restoring historical data

    History of Question: * The SAGE 100 Con database had over 30 companies in it and performance was "sluggish." * Backups were made of all companies and copied to another server for safekeeping. * A 2nd SQL instance was created and all companies between…
  • Sage 100 Contractor Sql in Report Writer

    FormerMember
    FormerMember
    Does anyone know where I could find information for the syntax that Sage 100 Contractor report writer requires with respect to SQL. I am trying to write a report for Committed Costs that is different from the report included with Sage, so I need to write…
  • Sage 100 Contractor nightly back up

    Sage 100 Contractor nightly back up has failed every night since we did our archive of prior year general ledger. How do find out what the problem is so that we can get the backups performing successfully again?
  • How to write SQL statement for percentage in subtotal and total rows?

    How to write SQL statement for percentage in subtotal and total rows? Getting % on detail rows is no problem, but when trying to get a % on the subtotal or total rows eludes me. Any help on this would be greatly appreciated. Thanks so much!
  • Accessing Sage 100 Contractor 2016 Database with Microsoft Access 2010

    How can the Sage 100 Contractor 2016 (version 20.4.51.0 or greater) databases be accessed using Microsoft Access 2010? I would like to link to the data source by creating a linked table. To do this I have created a Machine Data Source using ODBC in…
  • Use of SQL in Sage 100 Contractor Report Writer

    Can anyone tell me how to create a calculated field that has a SQL statement bringing in data from an unrelated table? I've looked at fields on other reports that I think are doing approximately the same thing but when I modify the SQL statement I keep…