Scripting

  • 1.  VB dotNet program, Sage 100 Premium 2014.4. On cu

    Posted 02-12-2015 06:37
    VB dotNet program, Sage 100 Premium 2014.4. On customer system only, not my dev system: oScript = New ProvideX.Script succeeds, but oScript.Init(InitPath) fails with ""Exception occurred. (Exception from HRESULT: 0x80020009 (DISP_E_EXCEPTION))"" InitPath verified correct Happens on their server and their workstations. Allow external access is checked. It had been working until this week on their system


  • 2.  RE: VB dotNet program, Sage 100 Premium 2014.4. On cu

    Posted 02-12-2015 06:41
    Phil, perhaps a windows update for .net or Visual Studio or some other windows program was installed on the customer's system?


  • 3.  RE: VB dotNet program, Sage 100 Premium 2014.4. On cu

    Posted 02-12-2015 07:03
    It does sound like an update that changed the sensitivity of part of the code. Perhaps this link might put your thinking in a useful direction: http://bit.ly/1DJohPg


  • 4.  RE: VB dotNet program, Sage 100 Premium 2014.4. On cu

    Posted 02-12-2015 15:24
    Hmmm...I am suspicious of these results but now that everyone is out of the system it works. Please tell me the BOI for entering sales orders doesn't need to be the only one in sales order to work...


  • 5.  RE: VB dotNet program, Sage 100 Premium 2014.4. On cu

    Posted 02-15-2015 16:30
    Maybe another BOI app is running during the day that is not shutting down properly?? WAG.


  • 6.  RE: VB dotNet program, Sage 100 Premium 2014.4. On cu

    Posted 02-15-2015 19:00
    Well, it worked the next day as well. Strange because I never did anything but add more messageboxes to try to figure out where it was screwing up...AFAIK there are no other BOI apps