Hello,
 
I'm bringing up this issue that our Director of Operations has been experiencing in WC-A.  Now that he has the ability to delete bin locations, he has been working through the long list of bins which are either no longer used or are duplicates.
 
For most of these locations, he is able to select the appropriate line, click on Delete and confirm.  This works as expected for most entries, but he is experiencing an issue on some of the items further down in the list, including entries where the Bin is listed as "NO BIN LOCATIONS".  When attempting to delete these (and anything further down the list), he clicks Delete, confirms the request, and then the screen changes to show ONLY the entry which was selected for deletion.  At this point, the WC-A window is essentially hung, and he cannot make any further changes and only sees the single entry.
 
Backing out and re-opening WC-A populates the full list again, and the record which was chosen for deletion WAS successfully deleted.  However, with the thousands of entries he is trying to clear up, backing out to re-open WC-A is putting a severe damper on the time it will take him to get through all the records.
 
I have checked his menu versions and all appears to be up to date.
 
I haven't been able to pinpoint if there is a particular entry in the list which causes the issue, given the number of items in the list.  
 
Sometimes, he is able to delete a row (or many) without the issue arising, but it appears to occur more frequently as he moves further down the table.
 
Any thoughts or ideas on what might be causing, or could resolve this issue?
 
Thanks,
Beau

Lynn,
 
Thank you for the clarification.  Should there be only a single "NO BIN LOC" entry?  We have hundreds of these entries.
 
Beau