Sage 100

 View Only
  • 1.  Any providex programmers out there know what cause

    Posted 12-16-2016 09:26
      |   view attached
    Any providex programmers out there know what causes this message? I use a custom Crystal Report for monitoring the System Activity Log. The user never reported an error to me - but that doesn't mean they actually received the error.


  • 2.  RE: Any providex programmers out there know what cause

    Posted 12-16-2016 09:55
    I'm a master developer, but I'm not much help today. Was there any postings before or after that one that might provide a clue what the user was doing? other than the typical user login messages?


  • 3.  RE: Any providex programmers out there know what cause

    Posted 12-16-2016 09:59
    Nope - no other errors posted for that user for that day.


  • 4.  RE: Any providex programmers out there know what cause

    Posted 12-16-2016 10:08
    I've found where the message is coming from - now I'm trying to figure out what triggers it


  • 5.  RE: Any providex programmers out there know what cause

    Posted 12-16-2016 10:17
    I am interested in the answer as well. I see this message occasionally at one client when they update the Make to Stock closing journal.


  • 6.  RE: Any providex programmers out there know what cause

    Posted 12-16-2016 10:51
    sometimes Sage adds good comments to their programs other times they do not. This is a case of not so much here at all. From walking backwards through the code (version 2016) the count (4158 in your the screenshot) is how many records are found in IM_DataEntryCostCalCommit table that match the tiers you are updating during physical count entry. I've read the code in the subroutine over and over and I'm pretty certain that the number reported is just how many records match and not how many were ""cleared"" I can't read the programmers mind but the counter is incremented as soon as a match is found not when the commit is actually cleared farther down in the code. So it looks to me like the message is supposed to tell you us how many records were cleared which would be ""unexpected"" when updating physical count entry. most likely that counter was moved and used for some other purpose but the message in the code for Physical count update is still reporting these as unexpected. I'm doing quite a bit of speculating but that is what it looks like without actually breaking into the code while it's executing.