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 :-(