title: MS Access Report Crashes in View Mode On Mouse Wheel
body: <p><strong>I have an MS Access report that crashes when the mouse wheel is used to scroll through the report in view mode.</strong>  I've been verbose.  <strong>For a quicker version, read bold text only.</strong></p>
  
  <p>Before I go further, when I say crashes Access, I mean a spinning wheel pops up and Access becomes unresponsive (i.e. "Not Responding").  The only way to get out of this state is to force Access to close.  No error codes or explanation are given.</p>
  
  <p>This problem only occurs in report view mode.  If I open the report in design, layout, or print mode there are no issues.  The issue only occurs when using the mouse wheel.  Scrolling with the vertical scroll bar or arrow keys poses no problem.  This issue is repeatable across users on different machines with different mice.  Though it is likely we're both running Access 2016 and Windows 7 Enterprise SP1.  I have not configured any "on mouse wheel" vba code anywhere in the database.</p>
  
  <p>The report itself contains ~20 fields, 2 very simple subreports (single tables with 2 columns liked off a single field on the main report), and a rather lengthy report body with 3 layers of grouping and roughly 150 rows sprinkled among the various groups.  The rows are retrieving longer memo fields (hundreds of characters per row).</p>
  
  <p>In addition, <strong>I have added a field that numbers each row (text box with control source=1, configured as a running sum "over all").  Oddly, if I delete the running sum text box, the problem goes away.  If I add it back again, the problem returns.</strong>  This is the only calculated field in the report.  All of the other data originate from queries.  I should point out that the report worked fine with the field that numbered each row prior to adding the two subreports.  So it seems that the combination of counting from 1 to 150 + subreports is overwhelming Access.  [This is surprising to me given that my database is fairly small - 15-20 tables with less than 1000 rows total.]</p>
  
  <p><a href="https://i.stack.imgur.com/UZ0vD.png" rel="nofollow noreferrer">Configuration of text box that seems to be causing the problem</a></p>
  
  <p><strong>Has anyone seen this problem before?  Does anyone know of a work around I could use to number each row versus just storing the row number in a table?</strong>  [I don't want to do it this way because I'd like the numbers to remain sequential and in order when a user adds or deletes a row or if a subset of rows is queried.  I could write code to detect changes and renumber, but I'm hoping for something simpler.]</p>