Sage 100

Often an "object required" error is caused by the Allow External Access flag not being clicked on in Company Maintenance.

Often an "object required" error is caused by the Allow External Access flag not being clicked on in Company Maintenance.

I don't know the reporting objects at all.  The only suggestion I have is to separate out your object creation into two pieces like this (which includes a permission check).

oBankCode = oSession.GetObject("GL_Bank_bus")

if oBankCode <> 0 then

        Set oBankCode = oSession.AsObject(oBankCode)

else        

        retVal = oSession.AsObject(oSession.UI).MessageBox("", "Access to GL_Bank_bus is required for the ... script to work.")

        exit sub

end if

Often an "object required" error is caused by the Allow External Access flag not being clicked on in Company Maintenance.

The following works for me on a 64-bit installation of 2023.  The LastErrorMsg and LastErrorNum properties of oSession may or may not contain useful information as they hold both errors and warnings.  They get overwritten throughout various methods too so you want to reset them before your method that may generate an error (can optionally check and store off the values prior to resetting them too) and then check them after your method that may generate an error.

If the nSY_ReportEngine variable comes back as a 0, then something in the ON_CREATE block of code of the SY_ReportEngine class is causing it to fail.  I would try a clean uninstall of the Sage 100 workstation, the 32 and 64-bit crystal runtimes, reboot, perform a clean install of the workstation (which should also install the crystal runtimes), and test the script again.

nSY_ReportEngine = 0 : oSession.LastErrorNum = "" : oSession.LastErrorMsg = "" : nSY_ReportEngine = oSession.NewObject("SY_ReportEngine")
oSession.AsObject(oSession.UI).MessageBox "nSY_ReportEngine: " & nSY_ReportEngine & vbCrLf & "oSession.LastErrorNum: " & oSession.LastErrorNum & vbCrLf & "oSession.LastErrorMsg: " & oSession.LastErrorMsg
oSession.DropObject nSY_ReportEngine
nSY_ReportEngine = 0

I don't know the reporting objects at all.  The only suggestion I have is to separate out your object creation into two pieces like this (which includes a permission check).

oBankCode = oSession.GetObject("GL_Bank_bus")

if oBankCode <> 0 then

        Set oBankCode = oSession.AsObject(oBankCode)

else        

        retVal = oSession.AsObject(oSession.UI).MessageBox("", "Access to GL_Bank_bus is required for the ... script to work.")

        exit sub

end if

The following works for me on a 64-bit installation of 2023.  The LastErrorMsg and LastErrorNum properties of oSession may or may not contain useful information as they hold both errors and warnings.  They get overwritten throughout various methods too so you want to reset them before your method that may generate an error (can optionally check and store off the values prior to resetting them too) and then check them after your method that may generate an error.

If the nSY_ReportEngine variable comes back as a 0, then something in the ON_CREATE block of code of the SY_ReportEngine class is causing it to fail.  I would try a clean uninstall of the Sage 100 workstation, the 32 and 64-bit crystal runtimes, reboot, perform a clean install of the workstation (which should also install the crystal runtimes), and test the script again.

nSY_ReportEngine = 0 : oSession.LastErrorNum = "" : oSession.LastErrorMsg = "" : nSY_ReportEngine = oSession.NewObject("SY_ReportEngine")oSession.AsObject(oSession.UI).MessageBox "nSY_ReportEngine: " & nSY_ReportEngine & vbCrLf & "oSession.LastErrorNum: " & oSession.LastErrorNum & vbCrLf & "oSession.LastErrorMsg: " & oSession.LastErrorMsgoSession.DropObject nSY_ReportEnginenSY_ReportEngine = 0

I don't know the reporting objects at all.  The only suggestion I have is to separate out your object creation into two pieces like this (which includes a permission check).

oBankCode = oSession.GetObject("GL_Bank_bus")

if oBankCode <> 0 then

        Set oBankCode = oSession.AsObject(oBankCode)

else        

        retVal = oSession.AsObject(oSession.UI).MessageBox("", "Access to GL_Bank_bus is required for the ... script to work.")

        exit sub

end if

Often an "object required" error is caused by the Allow External Access flag not being clicked on in Company Maintenance.

@David Overholt, yes, for example, I've used a BOI script to Print Preview all the module Setup Options and Trial Balance reports so that I could easily print them to PDF before running an upgrade. But, ironically, I prefer creating and using the custom reports, especially on Premium....

The following works for me on a 64-bit installation of 2023.  The LastErrorMsg and LastErrorNum properties of oSession may or may not contain useful information as they hold both errors and warnings.  They get overwritten throughout various methods too so you want to reset them before your method that may generate an error (can optionally check and store off the values prior to resetting them too) and then check them after your method that may generate an error.

If the nSY_ReportEngine variable comes back as a 0, then something in the ON_CREATE block of code of the SY_ReportEngine class is causing it to fail.  I would try a clean uninstall of the Sage 100 workstation, the 32 and 64-bit crystal runtimes, reboot, perform a clean install of the workstation (which should also install the crystal runtimes), and test the script again.

nSY_ReportEngine = 0 : oSession.LastErrorNum = "" : oSession.LastErrorMsg = "" : nSY_ReportEngine = oSession.NewObject("SY_ReportEngine")oSession.AsObject(oSession.UI).MessageBox "nSY_ReportEngine: " & nSY_ReportEngine & vbCrLf & "oSession.LastErrorNum: " & oSession.LastErrorNum & vbCrLf & "oSession.LastErrorMsg: " & oSession.LastErrorMsgoSession.DropObject nSY_ReportEnginenSY_ReportEngine = 0

I don't know the reporting objects at all.  The only suggestion I have is to separate out your object creation into two pieces like this (which includes a permission check).

oBankCode = oSession.GetObject("GL_Bank_bus")

if oBankCode <> 0 then

        Set oBankCode = oSession.AsObject(oBankCode)

else        

        retVal = oSession.AsObject(oSession.UI).MessageBox("", "Access to GL_Bank_bus is required for the ... script to work.")

        exit sub

end if

@David Overholt, yes, for example, I've used a BOI script to Print Preview all the module Setup Options and Trial Balance reports so that I could easily print them to PDF before running an upgrade. But, ironically, I prefer creating and using the custom reports, especially on Premium....

The following works for me on a 64-bit installation of 2023.  The LastErrorMsg and LastErrorNum properties of oSession may or may not contain useful information as they hold both errors and warnings.  They get overwritten throughout various methods too so you want to reset them before your method that may generate an error (can optionally check and store off the values prior to resetting them too) and then check them after your method that may generate an error.

If the nSY_ReportEngine variable comes back as a 0, then something in the ON_CREATE block of code of the SY_ReportEngine class is causing it to fail.  I would try a clean uninstall of the Sage 100 workstation, the 32 and 64-bit crystal runtimes, reboot, perform a clean install of the workstation (which should also install the crystal runtimes), and test the script again.

nSY_ReportEngine = 0 : oSession.LastErrorNum = "" : oSession.LastErrorMsg = "" : nSY_ReportEngine = oSession.NewObject("SY_ReportEngine")oSession.AsObject(oSession.UI).MessageBox "nSY_ReportEngine: " & nSY_ReportEngine & vbCrLf & "oSession.LastErrorNum: " & oSession.LastErrorNum & vbCrLf & "oSession.LastErrorMsg: " & oSession.LastErrorMsgoSession.DropObject nSY_ReportEnginenSY_ReportEngine = 0

I don't know the reporting objects at all.  The only suggestion I have is to separate out your object creation into two pieces like this (which includes a permission check).

oBankCode = oSession.GetObject("GL_Bank_bus")

if oBankCode <> 0 then

        Set oBankCode = oSession.AsObject(oBankCode)

else        

        retVal = oSession.AsObject(oSession.UI).MessageBox("", "Access to GL_Bank_bus is required for the ... script to work.")

        exit sub

end if

Often an "object required" error is caused by the Allow External Access flag not being clicked on in Company Maintenance.

I have been some more testing on the script program. Once I deleted the C.O Button Link on the Sales Order Screen, and re-added it with the setting to "Execute Script on Server".  It works when I am on the server as the domain administrator user. 

On the clients' machine, nothing happens. No more script errors, but not report either. It does work in MAS90 mode. 

The service account is setup to run as Domain\Administrator.

Also with setting "Execute Script on Client" - I get the above error messages.

Any suggestions will be appreciated.

Thank you

Michael

@David Overholt, yes, for example, I've used a BOI script to Print Preview all the module Setup Options and Trial Balance reports so that I could easily print them to PDF before running an upgrade. But, ironically, I prefer creating and using the custom reports, especially on Premium....

The following works for me on a 64-bit installation of 2023.  The LastErrorMsg and LastErrorNum properties of oSession may or may not contain useful information as they hold both errors and warnings.  They get overwritten throughout various methods too so you want to reset them before your method that may generate an error (can optionally check and store off the values prior to resetting them too) and then check them after your method that may generate an error.

If the nSY_ReportEngine variable comes back as a 0, then something in the ON_CREATE block of code of the SY_ReportEngine class is causing it to fail.  I would try a clean uninstall of the Sage 100 workstation, the 32 and 64-bit crystal runtimes, reboot, perform a clean install of the workstation (which should also install the crystal runtimes), and test the script again.

nSY_ReportEngine = 0 : oSession.LastErrorNum = "" : oSession.LastErrorMsg = "" : nSY_ReportEngine = oSession.NewObject("SY_ReportEngine")oSession.AsObject(oSession.UI).MessageBox "nSY_ReportEngine: " & nSY_ReportEngine & vbCrLf & "oSession.LastErrorNum: " & oSession.LastErrorNum & vbCrLf & "oSession.LastErrorMsg: " & oSession.LastErrorMsgoSession.DropObject nSY_ReportEnginenSY_ReportEngine = 0

I don't know the reporting objects at all.  The only suggestion I have is to separate out your object creation into two pieces like this (which includes a permission check).

oBankCode = oSession.GetObject("GL_Bank_bus")

if oBankCode <> 0 then

        Set oBankCode = oSession.AsObject(oBankCode)

else        

        retVal = oSession.AsObject(oSession.UI).MessageBox("", "Access to GL_Bank_bus is required for the ... script to work.")

        exit sub

end if

Often an "object required" error is caused by the Allow External Access flag not being clicked on in Company Maintenance.

It works in MAS90 Mode from the client but not Advanced?  What path is being returned for the path root?

retMSG = oSession.AsObject(oSession.UI).MessageBox("", oSession.pathRoot)

I have been some more testing on the script program. Once I deleted the C.O Button Link on the Sales Order Screen, and re-added it with the setting to "Execute Script on Server".  It works when I am on the server as the domain administrator user. 

On the clients' machine, nothing happens. No more script errors, but not report either. It does work in MAS90 mode. 

The service account is setup to run as Domain\Administrator.

Also with setting "Execute Script on Client" - I get the above error messages.

Any suggestions will be appreciated.

Thank you

Michael

@David Overholt, yes, for example, I've used a BOI script to Print Preview all the module Setup Options and Trial Balance reports so that I could easily print them to PDF before running an upgrade. But, ironically, I prefer creating and using the custom reports, especially on Premium....

The following works for me on a 64-bit installation of 2023.  The LastErrorMsg and LastErrorNum properties of oSession may or may not contain useful information as they hold both errors and warnings.  They get overwritten throughout various methods too so you want to reset them before your method that may generate an error (can optionally check and store off the values prior to resetting them too) and then check them after your method that may generate an error.

If the nSY_ReportEngine variable comes back as a 0, then something in the ON_CREATE block of code of the SY_ReportEngine class is causing it to fail.  I would try a clean uninstall of the Sage 100 workstation, the 32 and 64-bit crystal runtimes, reboot, perform a clean install of the workstation (which should also install the crystal runtimes), and test the script again.

nSY_ReportEngine = 0 : oSession.LastErrorNum = "" : oSession.LastErrorMsg = "" : nSY_ReportEngine = oSession.NewObject("SY_ReportEngine")oSession.AsObject(oSession.UI).MessageBox "nSY_ReportEngine: " & nSY_ReportEngine & vbCrLf & "oSession.LastErrorNum: " & oSession.LastErrorNum & vbCrLf & "oSession.LastErrorMsg: " & oSession.LastErrorMsgoSession.DropObject nSY_ReportEnginenSY_ReportEngine = 0

I don't know the reporting objects at all.  The only suggestion I have is to separate out your object creation into two pieces like this (which includes a permission check).

oBankCode = oSession.GetObject("GL_Bank_bus")

if oBankCode <> 0 then

        Set oBankCode = oSession.AsObject(oBankCode)

else        

        retVal = oSession.AsObject(oSession.UI).MessageBox("", "Access to GL_Bank_bus is required for the ... script to work.")

        exit sub

end if

Often an "object required" error is caused by the Allow External Access flag not being clicked on in Company Maintenance.

That was it. 

The oSession.pathRoot was pointing to the C drive.

I change to script to point the UNC path of the server and removed the path root line. Everything is working from the client now. Thank you

It works in MAS90 Mode from the client but not Advanced?  What path is being returned for the path root?

retMSG = oSession.AsObject(oSession.UI).MessageBox("", oSession.pathRoot)

I have been some more testing on the script program. Once I deleted the C.O Button Link on the Sales Order Screen, and re-added it with the setting to "Execute Script on Server".  It works when I am on the server as the domain administrator user. 

On the clients' machine, nothing happens. No more script errors, but not report either. It does work in MAS90 mode. 

The service account is setup to run as Domain\Administrator.

Also with setting "Execute Script on Client" - I get the above error messages.

Any suggestions will be appreciated.

Thank you

Michael

@David Overholt, yes, for example, I've used a BOI script to Print Preview all the module Setup Options and Trial Balance reports so that I could easily print them to PDF before running an upgrade. But, ironically, I prefer creating and using the custom reports, especially on Premium....

The following works for me on a 64-bit installation of 2023.  The LastErrorMsg and LastErrorNum properties of oSession may or may not contain useful information as they hold both errors and warnings.  They get overwritten throughout various methods too so you want to reset them before your method that may generate an error (can optionally check and store off the values prior to resetting them too) and then check them after your method that may generate an error.

If the nSY_ReportEngine variable comes back as a 0, then something in the ON_CREATE block of code of the SY_ReportEngine class is causing it to fail.  I would try a clean uninstall of the Sage 100 workstation, the 32 and 64-bit crystal runtimes, reboot, perform a clean install of the workstation (which should also install the crystal runtimes), and test the script again.

nSY_ReportEngine = 0 : oSession.LastErrorNum = "" : oSession.LastErrorMsg = "" : nSY_ReportEngine = oSession.NewObject("SY_ReportEngine")oSession.AsObject(oSession.UI).MessageBox "nSY_ReportEngine: " & nSY_ReportEngine & vbCrLf & "oSession.LastErrorNum: " & oSession.LastErrorNum & vbCrLf & "oSession.LastErrorMsg: " & oSession.LastErrorMsgoSession.DropObject nSY_ReportEnginenSY_ReportEngine = 0

I don't know the reporting objects at all.  The only suggestion I have is to separate out your object creation into two pieces like this (which includes a permission check).

oBankCode = oSession.GetObject("GL_Bank_bus")

if oBankCode <> 0 then

        Set oBankCode = oSession.AsObject(oBankCode)

else        

        retVal = oSession.AsObject(oSession.UI).MessageBox("", "Access to GL_Bank_bus is required for the ... script to work.")

        exit sub

end if

Often an "object required" error is caused by the Allow External Access flag not being clicked on in Company Maintenance.

That was it. 

The oSession.pathRoot was pointing to the C drive.

I change to script to point the UNC path of the server and removed the path root line. Everything is working from the client now. Thank you

It works in MAS90 Mode from the client but not Advanced?  What path is being returned for the path root?

retMSG = oSession.AsObject(oSession.UI).MessageBox("", oSession.pathRoot)

I have been some more testing on the script program. Once I deleted the C.O Button Link on the Sales Order Screen, and re-added it with the setting to "Execute Script on Server".  It works when I am on the server as the domain administrator user. 

On the clients' machine, nothing happens. No more script errors, but not report either. It does work in MAS90 mode. 

The service account is setup to run as Domain\Administrator.

Also with setting "Execute Script on Client" - I get the above error messages.

Any suggestions will be appreciated.

Thank you

Michael

@David Overholt, yes, for example, I've used a BOI script to Print Preview all the module Setup Options and Trial Balance reports so that I could easily print them to PDF before running an upgrade. But, ironically, I prefer creating and using the custom reports, especially on Premium....

The following works for me on a 64-bit installation of 2023.  The LastErrorMsg and LastErrorNum properties of oSession may or may not contain useful information as they hold both errors and warnings.  They get overwritten throughout various methods too so you want to reset them before your method that may generate an error (can optionally check and store off the values prior to resetting them too) and then check them after your method that may generate an error.

If the nSY_ReportEngine variable comes back as a 0, then something in the ON_CREATE block of code of the SY_ReportEngine class is causing it to fail.  I would try a clean uninstall of the Sage 100 workstation, the 32 and 64-bit crystal runtimes, reboot, perform a clean install of the workstation (which should also install the crystal runtimes), and test the script again.

nSY_ReportEngine = 0 : oSession.LastErrorNum = "" : oSession.LastErrorMsg = "" : nSY_ReportEngine = oSession.NewObject("SY_ReportEngine")oSession.AsObject(oSession.UI).MessageBox "nSY_ReportEngine: " & nSY_ReportEngine & vbCrLf & "oSession.LastErrorNum: " & oSession.LastErrorNum & vbCrLf & "oSession.LastErrorMsg: " & oSession.LastErrorMsgoSession.DropObject nSY_ReportEnginenSY_ReportEngine = 0

I don't know the reporting objects at all.  The only suggestion I have is to separate out your object creation into two pieces like this (which includes a permission check).

oBankCode = oSession.GetObject("GL_Bank_bus")

if oBankCode <> 0 then

        Set oBankCode = oSession.AsObject(oBankCode)

else        

        retVal = oSession.AsObject(oSession.UI).MessageBox("", "Access to GL_Bank_bus is required for the ... script to work.")

        exit sub

end if

Often an "object required" error is caused by the Allow External Access flag not being clicked on in Company Maintenance.