Not directly, but you should be able to script something that triggers SQLCMD (a free Microsoft tool) with the correct parameters.

That being said, it is MUCH easier to pull data on a frequent schedule, vs pushing on demand.

I execute stored procedures (functions) on the server using SQL statements with ODBC. Works great for me.

Oh that's cool! Do you have any resources you can point me to to learn more on that?

Are you talking about through something like this?

Set dbConn = CreateObject("ADODB.Connection")

I guess this would work, but we only use that method for a query / record set now.  The reason we use SQLCMD is to capture any results / error messages in a log file (-o), and it doesn't tend to lock-up the way VBScript working with SQL data tends to do on occasion.

Are you talking about through something like this?

Set dbConn = CreateObject("ADODB.Connection")

I guess this would work, but we only use that method for a query / record set now.  The reason we use SQLCMD is to capture any results / error messages in a log file (-o), and it doesn't tend to lock-up the way VBScript working with SQL data tends to do on occasion.

I'm using ScriptBasic's ODBC extension module. I'm not a big fan of ADO as it's bloatware with everything being an object.

It works for simple things and doesn't require any additional software being installed for it to work, but I agree ADO is not ideal for complex use.

Kevin M said:

The reason we use SQLCMD is to capture any results / error messages in a log file (-o), and it doesn't tend to lock-up the way VBScript working with SQL data tends to do on occasion.

Could you expand upon that more? I'm currently drafting up a script and want to work the SQLCMD route

I tried using the Accept button event in one of my scripts. It caused a Windows exception error. I ended up using the after write event which worked as expected.

Keep in mind that using VBScript and ADO inside a hosted COM component has limitations.

A good example is the SQLite wrapped ActiveX control I tried using with WSH It dies with a message saying unable to load with no error or reason. The control works with ScriptBasic and everything else I tried it with.

These are batch file commands... used in processes initiated outside of Sage 100 (not scripts) so you're on your own for that part of it.

This captures the SQL return messages (like "2 rows affected", or a connection error) into a temp log file, which I copy into a daily log file, for potential reference when troubleshooting.

SET TodayLogFile=E:\Accounting\logs\Refresh_%date:~-4,4%%date:~-10,2%%date:~-7,2%.txt
SET TempLogFile=E:\Accounting\logs\Refresh.txt

ECHO %date% %time% Starting Refresh >> %TodayLogFile%
sqlcmd -S Server\Instance -E -d MAS_ABC -Q "update ... blah blah blah;" -o %TempLogFile%
type %TempLogFile% >> %TodayLogFile%
ECHO %date% %time% Finishing Refresh >> %TodayLogFile%