Sage 100 has two different database options. 

The Standard and Advanced versions run on a back-end called Providex, where the ODBC access is read-only. (This is the SOTAMAS90 connection John mentions).

If they run Sage 100 Premium, the back end is in MS SQL, but you still do not want to edit data directly through SQL commands.  The business logic is handled through the Sage 100's API (called the BOI / Business Object Interface), which is not quick to learn but must be used so you don't corrupt the data.

I believe someone (MBA?) created a REST API as a bridge to Sage 100 BOI, and there is a program called Insynch we've used to push / pull data to and from websites.  Sage is also developing an interface through Office 365 based connectors.  I'm sure I'm forgetting to mention other options and there are more than a few threads here on Sage City about integrating Sage 100 with web functions.  You'd be well served by reading as many of them as you can find.

Sage 100 has two different database options. 

The Standard and Advanced versions run on a back-end called Providex, where the ODBC access is read-only. (This is the SOTAMAS90 connection John mentions).

If they run Sage 100 Premium, the back end is in MS SQL, but you still do not want to edit data directly through SQL commands.  The business logic is handled through the Sage 100's API (called the BOI / Business Object Interface), which is not quick to learn but must be used so you don't corrupt the data.

I believe someone (MBA?) created a REST API as a bridge to Sage 100 BOI, and there is a program called Insynch we've used to push / pull data to and from websites.  Sage is also developing an interface through Office 365 based connectors.  I'm sure I'm forgetting to mention other options and there are more than a few threads here on Sage City about integrating Sage 100 with web functions.  You'd be well served by reading as many of them as you can find.