Sage 100

 View Only
  • 1.  Sage 100 v2013 Std - Client is encountering error

    Posted 12-23-2013 17:33
    Sage 100 v2013 Std - Client is encountering error when trying to open IT_Item. Error 22.. Ivalid compound statement Program. SY_GRIDHANDLER.PVC Statement. 2290 Class. IT_Item_Ui Method. SetGridHeaders Only thing I know tonight.


  • 2.  RE: Sage 100 v2013 Std - Client is encountering error

    Posted 12-24-2013 03:54
    Any Custom Office changes?


  • 3.  RE: Sage 100 v2013 Std - Client is encountering error

    Posted 12-24-2013 04:36
    That is what I am thinking. Just starting happening though and there haven't been any changes recently. Will double check.


  • 4.  RE: Sage 100 v2013 Std - Client is encountering error

    Posted 12-24-2013 04:53
    I have no one using ebus so don't know what that screen looks like, but maybe someone modified how the lines are? (not via Cus Ofc) Then you might have to delete the rec in... SY_PERSONALIZE? I always have to go hunting. Also, is this happening to more than one person?


  • 5.  RE: Sage 100 v2013 Std - Client is encountering error

    Posted 12-24-2013 05:02
    Only one person, just started on Friday.


  • 6.  RE: Sage 100 v2013 Std - Client is encountering error

    Posted 12-24-2013 05:05
    Yeah, sounding like their customization (rearranging things on the lines, etc) is fubar.


  • 7.  RE: Sage 100 v2013 Std - Client is encountering error

    Posted 12-24-2013 05:44
    Had several gridhandler issues in the past and all but one was solved by resetting the grid in panel Settings. The one odd ball had a corrupt Inventory item on an invoice


  • 8.  RE: Sage 100 v2013 Std - Client is encountering error

    Posted 12-24-2013 06:02
    Yeah, the bad part is when the screen is so screwed you can't even get to the Reset.


  • 9.  RE: Sage 100 v2013 Std - Client is encountering error

    Posted 12-26-2013 01:16
    In case it turns out to be not related to the customization go to eBusiness Mgr / Setup / Category Maintenance and pull up a category to see if you get a ""friendlier"" version of the error.