Sage 100

We have a VI job to import sales orders from a text file.

The script to reformat the file into a Sage compatible format has a section that opens a connection to Sage data via a DSN and searches for the "UDF_WebID" and returns back the customer number.  This script works on the server, but not on workstations ... it's the connection to Sage data that is failing (either using SOTAMAS90 or a silent DSN).  The client is on v2017 Standard.  Our last step in troubleshooting is to disable TrendMicro, but the same version of TrendMicro, I believe, is on the server where it works and on the workstation where it doesn't work.  Our 'admin' level account is logged into both machines, so it shouldn't be security related.

If you have ideas for the above, we're open to suggestions.

However, my plan B is to see if we can add a perform logic (?) line to the VI job so that it will find the customer number as part of the VI job.  I think I read that someone had done some kind of lookup like that before (I think it was to find a name and bring back the customer number).  If anyone remembers this, can you send me the steps that you did, please.

Thanks in advance, Robert

#VI

------------------------------
Robert White
Munjal White Consulting Co.
Toronto ON
------------------------------

When I looked quickly, Excel queries were crashing too.  We could get the table list, select columns, but as soon as the query was triggered (to return data to Excel), the crash.  So there is something wrong with ODBC queries in general, not the script.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

@Kevin Moyes - From a long time ago on Sage City an ODBC locking issue was reported with Trend Micro and this what was reported to have worked:

Setting: "Terminate programs that exhibit abnormal behavior associated with exploit attacks"

under Devices > Desktop > Configure Policy > Behavior Monitoring > Ransomware Protection > Anti-Exploit Protection

------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA
------------------------------

Is the script actually using a DSN or is it specifying the connection string (including paths)?
If the workstation was installed on the server from the local path and the script is using local path in the connection string, then that would cause a pathing issue when launched from a workstation that would have to access sage 100 from a UNC or mapped drive letter.
As for the perform logic, that is viable route, assuming the UDF_WebID is in AR_Customer, you should be able to use the After Read Perform Type, which occurs after a line is read from the source file, then use the child object for the CustomerNo field to call the GetResultSets method with the filter on the UDF.  You could also do this as a calculation in the CustomerNo field instead.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------