Sage 100

 View Only
  • 1.  Gross Requirement Report - Multiple User File Lock

    Posted 11-21-2014 08:44
    Gross Requirement Report - Multiple User File Locking I upgraded a client from 4.4 to 2014 over the weekend. In the old version, multiple users could access the BM Gross Requirements report at the same time. Now as soon as one user logs in the other users get a ""The report selection table is in use"" error. It appears that both versions use the same work file but certainly react differently. Did I do something wrong or did Sage change file locking and is there a possible work around?


  • 2.  RE: Gross Requirement Report - Multiple User File Lock

    Posted 11-21-2014 13:13
    Interesting that a temporary work file isn't created.


  • 3.  RE: Gross Requirement Report - Multiple User File Lock

    Posted 11-21-2014 13:55
    Tested it over here on my test data and the same thing happened to me. Strange.


  • 4.  RE: Gross Requirement Report - Multiple User File Lock

    Posted 11-21-2014 21:27
    Happens in 4.50 too. It if it worked in 4.40 then they must have added the code to create a lock file for the report in \mas90\Lock\xxx in one of the product updates. If it can't create the file (because it exists already from 1st user) then that selection table error occurs. Someone may have reported it to Support as a scenario where if User A prints, then User B prints, User A's bills are included with User B's print job. They fixed it the ""easy way"" by locking down User B. @JeffSchwenk is right. Learned from a mod I did that BM_ComponentReportSelection.m4t is a temp file used as the selection table to store the bills selected on the grid. This in addition to the normal temp WRK file from any Crystal worktable rpt. The WRK file is properly unique but the the former is not. This can get fixed by by adding a Session ID field or similar as part of the key in the former to make it unique. Then no need for CreateLock() function in the UI program. I would consider this a bug but they will consider it a WAD :-(