Sage 100

OK. Another question for #scripting experts (maybe). One of the scripts that we've created for a client seems to have some strange behavior. Occasionally the script will start, and on the second (not the first, but the second) call to anything #BOI related we get an Error #88. It doesn't matter what the call is. I thought for a while that it was related to an object that we instantiated, so I added an oScript.DebugPrint before the object, and now the script fails when I get to the oScript.DebugPrint. This happens 40% of the time. The error is happening on the client machine (MAS200) but I can't reproduce on my MAS90 installation. We haven't been able to reproduce this error consistently on the MAS200 installation, but don't let that #MonkeyWrench scare you off. Thanks in advance!

I'm no scripting expert but I know I have had problems with scripts and MAS 200 due to the server side processing.

Good suggestion, @ThereseLogeais. I ran the system in MAS90 mode, and I got the same error (on the second order I created), so that's out.

What is the full Error 88 info and could you post a code snippet ..