Sage 100

1. You have Execute Script on Client set in the button properties within Customizer. Change to Execute Script on Server. 
2. You don't have External Access turned on in Company Maintenance. Hey I know, unlikely but if you just made a Copy company then take a look.
3. Old problem with Premium that shouldn't still be a problem. On App Server the masSql.Settings file in \mas90\Home, the "Driver=" info on the CONNECT= line is malformed.

1. You have Execute Script on Client set in the button properties within Customizer. Change to Execute Script on Server. 
2. You don't have External Access turned on in Company Maintenance. Hey I know, unlikely but if you just made a Copy company then take a look.
3. Old problem with Premium that shouldn't still be a problem. On App Server the masSql.Settings file in \mas90\Home, the "Driver=" info on the CONNECT= line is malformed.

Yep. So below is a snippet from a larger Pre-Validation on CustomerName script I did to reject a duplicate customer name keyed into Cust Maint. Main logic runs first to ID a dupe customer name was found then 2nd script PlaySoundWkstn.vbs runs from client to audibly speak the words "This customer name is already used". It uses the Windows Text To Speech (TTS) API. Although you don't need sound the principles are otherwise same for your button but set Execute Script on Server so can you do your oLines.Write() first then fire off client script at the end.

Arguments: I didn't need to pass any myself but it shouldn't be a problem:
* Append your args to the vbsCMD below
* Inside 2nd script use WScript.Arguments(n) to evaluate the args. Here's an example - VBS ex on using args
* I seem to recall needing to name 2nd script with a .VBS extension (not .TXT)

If oSession.CS Then 'CS means running on Adv or Premium

'Set location for Workstation Script.
WkstnScript = oSession.PathCSRoot + "CM\Script\PlaySoundWkstn.vbs" 'Substitute w/ your VBS

WSH = "WScript.exe " 'May need to hard-code that to C:\Windows\SysWow64\WScript.exe
vbsCMD = CHR(34) & WSH & WkstnScript & CHR(34) 'Form the o/s cmd to run it. Add args here too.
oScript.Execute("ShellCMD$ = " & vbsCMD) 'Pass the cmd into a pvx variable ShellCMD$

'Fire off the script at the workstation. The [wdx] indicates run from the client.
oScript.Execute("CALL "+CHR(34)+"[wdx]SYZDLL;SHELL_AND_WAIT"+CHR(34)+",ShellCMD$")

Else

'Tap into TTS feature. More info can be found here: http://goo.gl/cM6dYJ
If IsObject(oVoice) = False Then
  Set oVoice = CreateObject("SAPI.SpVoice")
End If

Words = "This customer name is already used."
retVal = oVoice.Speak(Words)

End If

1. You have Execute Script on Client set in the button properties within Customizer. Change to Execute Script on Server. 
2. You don't have External Access turned on in Company Maintenance. Hey I know, unlikely but if you just made a Copy company then take a look.
3. Old problem with Premium that shouldn't still be a problem. On App Server the masSql.Settings file in \mas90\Home, the "Driver=" info on the CONNECT= line is malformed.

Yep. So below is a snippet from a larger Pre-Validation on CustomerName script I did to reject a duplicate customer name keyed into Cust Maint. Main logic runs first to ID a dupe customer name was found then 2nd script PlaySoundWkstn.vbs runs from client to audibly speak the words "This customer name is already used". It uses the Windows Text To Speech (TTS) API. Although you don't need sound the principles are otherwise same for your button but set Execute Script on Server so can you do your oLines.Write() first then fire off client script at the end.

Arguments: I didn't need to pass any myself but it shouldn't be a problem:
* Append your args to the vbsCMD below
* Inside 2nd script use WScript.Arguments(n) to evaluate the args. Here's an example - VBS ex on using args
* I seem to recall needing to name 2nd script with a .VBS extension (not .TXT)

If oSession.CS Then 'CS means running on Adv or Premium

'Set location for Workstation Script.
WkstnScript = oSession.PathCSRoot + "CM\Script\PlaySoundWkstn.vbs" 'Substitute w/ your VBS

WSH = "WScript.exe " 'May need to hard-code that to C:\Windows\SysWow64\WScript.exe
vbsCMD = CHR(34) & WSH & WkstnScript & CHR(34) 'Form the o/s cmd to run it. Add args here too.
oScript.Execute("ShellCMD$ = " & vbsCMD) 'Pass the cmd into a pvx variable ShellCMD$

'Fire off the script at the workstation. The [wdx] indicates run from the client.
oScript.Execute("CALL "+CHR(34)+"[wdx]SYZDLL;SHELL_AND_WAIT"+CHR(34)+",ShellCMD$")

Else

'Tap into TTS feature. More info can be found here: http://goo.gl/cM6dYJ
If IsObject(oVoice) = False Then
  Set oVoice = CreateObject("SAPI.SpVoice")
End If

Words = "This customer name is already used."
retVal = oVoice.Speak(Words)

End If

1. You have Execute Script on Client set in the button properties within Customizer. Change to Execute Script on Server. 
2. You don't have External Access turned on in Company Maintenance. Hey I know, unlikely but if you just made a Copy company then take a look.
3. Old problem with Premium that shouldn't still be a problem. On App Server the masSql.Settings file in \mas90\Home, the "Driver=" info on the CONNECT= line is malformed.

Yep. So below is a snippet from a larger Pre-Validation on CustomerName script I did to reject a duplicate customer name keyed into Cust Maint. Main logic runs first to ID a dupe customer name was found then 2nd script PlaySoundWkstn.vbs runs from client to audibly speak the words "This customer name is already used". It uses the Windows Text To Speech (TTS) API. Although you don't need sound the principles are otherwise same for your button but set Execute Script on Server so can you do your oLines.Write() first then fire off client script at the end.

Arguments: I didn't need to pass any myself but it shouldn't be a problem:
* Append your args to the vbsCMD below
* Inside 2nd script use WScript.Arguments(n) to evaluate the args. Here's an example - VBS ex on using args
* I seem to recall needing to name 2nd script with a .VBS extension (not .TXT)

If oSession.CS Then 'CS means running on Adv or Premium

'Set location for Workstation Script.
WkstnScript = oSession.PathCSRoot + "CM\Script\PlaySoundWkstn.vbs" 'Substitute w/ your VBS

WSH = "WScript.exe " 'May need to hard-code that to C:\Windows\SysWow64\WScript.exe
vbsCMD = CHR(34) & WSH & WkstnScript & CHR(34) 'Form the o/s cmd to run it. Add args here too.
oScript.Execute("ShellCMD$ = " & vbsCMD) 'Pass the cmd into a pvx variable ShellCMD$

'Fire off the script at the workstation. The [wdx] indicates run from the client.
oScript.Execute("CALL "+CHR(34)+"[wdx]SYZDLL;SHELL_AND_WAIT"+CHR(34)+",ShellCMD$")

Else

'Tap into TTS feature. More info can be found here: http://goo.gl/cM6dYJ
If IsObject(oVoice) = False Then
  Set oVoice = CreateObject("SAPI.SpVoice")
End If

Words = "This customer name is already used."
retVal = oVoice.Speak(Words)

End If

1. You have Execute Script on Client set in the button properties within Customizer. Change to Execute Script on Server. 
2. You don't have External Access turned on in Company Maintenance. Hey I know, unlikely but if you just made a Copy company then take a look.
3. Old problem with Premium that shouldn't still be a problem. On App Server the masSql.Settings file in \mas90\Home, the "Driver=" info on the CONNECT= line is malformed.