Sage 100

Calling any script Guru. I installed the reverse journal entry script that Steve Malmgren has demoed in MAS 90 v4.5 prior to any PU's being released. It worked! So I copied it over to my office copy of MAS 200 PU2. Now I get the following error regarding an object being required. The error displays on my WIN 7 64 OS workstation. The script is set to execute on the client. When I set the script to execute on the server, the login panel displays on the server console. Once I login (at the server console) the script executes. So I guess my question is, what is preventing the script from displaying the login panel on my workstation? Thanks in advance.

As you discovered - your first messages are the result of the fact that advanced scripting methods and objects are not available in the MAS 200 client. The script must run under the context of the ""pvxwin32.exe"" that runs on the MAS 200 server or in a MAS 90 environment. Your login prompt is due to the fact that he uses the ODBC to retrieve the journal entry which requires login credentials that you must edit into the script ""BT_reverseGL.vbs"" if security is enabled. He uses the ODBC because there is no GL_DetailPosting business object available with which to retrieve data about the selected entry. He points all this out if you read the comments in the code and he also points out that this script will not work with batches.

So is there a solution to the pvxwin32.exe situation? I can live with the security issue.

Apparently, in the MAS 200 client environment the ""pvxwin32.exe"" program doesn't provide the business object model. Is there a reason you can't just have it run on the server?

Under the present configuration, no as the challenge for the ODBC connection displays at the server console, not at the workstation. While it appears that the fix is to embed the user information in the script, that isn't the most secure approach.

There are many holes in the design of advanced scripting. Don't get me started. At least this one has SOME kind of worked around.

Create a silent ODBC DSN for MAS on the MAS 200 server and use that DSN in the script. This provides an ODBC connection without the challenge on the server. Silent ODBC connections have some security risks that need to be managed/controlled.

So is this where you would do it? Substitue the silent connnection name for sotamas90 and then delete the UID and PWD string? sConnection = ""DSN=SOTAMAS90;UID=;COMPANY=ABC;PWD=

That did the trick. I set up a silent system DSN on the server, replaced the SOTAMAS90 string with the new name and deleted the UID and PWD since they were no longer needed.