If SQL is on the same network as the Sage server, you might be able to use VI instead of any kind of external / custom programming.

If the data needs to bridge over the internet, something like InSynch might be worth considering (instead of developing something custom / in-house).

For a real-time interactive user interface using the O365 connector Sage has built (reference the Sage Contacts function), that would require an MS Power App... but I don't know of anyone actually doing this in production.  (I've only seen it demonstrated).

If SQL is on the same network as the Sage server, you might be able to use VI instead of any kind of external / custom programming.

If the data needs to bridge over the internet, something like InSynch might be worth considering (instead of developing something custom / in-house).

For a real-time interactive user interface using the O365 connector Sage has built (reference the Sage Contacts function), that would require an MS Power App... but I don't know of anyone actually doing this in production.  (I've only seen it demonstrated).

ScriptBasic uses ODBC and BOI with a traditional BASIC syntax. Open source and free.

See my profile for more info

I wonder if Sage 100 was open source and free would people stop using it?