Issues opening Sales Order with Script Sales_Order_UI

I have used this code for years me and a handful of others, but we have a few new users that are having issues and can't appear to use my app to open Sage Sales Order.

The only indicator they get is SO_SalesOrder_UI in a message box.

Here is the code I have been using to open it:

ChDrive "T"
ChDir "T:\MAS90\HOME"
Shell ("T:\MAS90\HOME\pvxwin32.exe ..\LAUNCHER\SOTA.INI ..\SOA\Startup.M4P -ARG DIRECT UION " & strUser & " " & strPwd & " CMP SO_SalesOrder_UI ") & strSONO

any ideas on how to fix this issue?

We use this code in quite a few Microsoft Access Apps

Parents
  • When the issue occurs, do either of the following apply?

    Does the sales order number have any single or double quotes (or other weird characters) in it? 

    Is the sales order number less than 7 characters?

    Have you checked the users' roles to make sure they have adequate access?

Reply
  • When the issue occurs, do either of the following apply?

    Does the sales order number have any single or double quotes (or other weird characters) in it? 

    Is the sales order number less than 7 characters?

    Have you checked the users' roles to make sure they have adequate access?

Children
  • in reply to David Speck

    I can user the "user's id" and "password" from my computer with and access the same sales order number, but I can't from the other computer.  That leads me to believe that it's not the role so much as it maybe a file a file that is missing in windows folders or c:\Sage folder?  Maybe?

  • in reply to momiebear

    Did you install the Sage workstation program on the new user's machines?  It looks like you are running from a mapped drive, but there are required program resources needed locally for anything Sage 100 to work.

  • in reply to momiebear

    Have you tried reinstalling the workstation and making sure they have appropriate NTFS permissions to the Sage 100 directories for both the server and workstation (if Advanced)?

  • in reply to Kevin M

    I don't normally install the workstations, so how can I determine by looking at their computer that this has or hasn't been done.  If I look at my system I can see that I have SAGE 100 2018 Workstation App.  Is this what I would need to do at their workstation?

  • in reply to momiebear

    Yes.  If you can't log in to Sage 100 properly from the machine, the workstation software needs to be installed.

  • in reply to Kevin M

    Yes, The workstations do work correctly when we login to SAGE from every machine.  I just have Microsoft applications that I have built that READ from SAGE and will open SAGE Sales Orders, Invoices, Jobs, Customer Maintenance, So on and So forth, but on some machines it fails to launch, People who have the same Roles as I do, but it doesn't work.  I can hard code a user ID and Password that I know works on my computer and will work on other computers, but it will not work on their computer.  SO, it doesn't appear to be Permissions, and it doesn't appear to be Role, but it may be computer, computer setting or installation.  But, that is my limited knowledge.  So I get with my it guru and have him try the re-install and to check NTFS and then I will post the results thereafter.  If you think of anything else.  Let me know!  Thanks!

  • in reply to momiebear

    After reviewing the issue with my IT department and sharing my findings thus far, IT was able to further narrow the issue down to EBIZ and reassures that a patch will fix the issues by this weekend.  Thank you all for your help!