Incidentely I just have it reading cell coordinates, not boarders or other information beyond the text in the cells. Personal website wrote: when using MS office 2016 as a direct enterprise install, or MS office 365, I notice a real slow down when using ms excel and using the arrow keys to navigate between cells.I have noticed this issue for about the last 8 months using the NVDA next builds, but just haven't gotten around to reporting it. I use Excel daily for work now so this is getting to be a real issue for me. Sometimes it can take up to 2 seconds to move between cells.sometimes there is no speech at all when moving between cells, particularly if i have entered something into a cell and then hit enter to update it.I have noticed this is particularly present when inputting numbers, which you can do by using the price column in my excel sheet i've attached. Screen Updating = True THe error is Compile error, Method or data member not found Anyone has a clue what the problem is? when using MS office 2016 as a direct enterprise install, or MS office 365, I notice a real slow down when using ms excel and using the arrow keys to navigate between cells.Hi I am trying to build a VBA modul, two lines with the command (Application.
This course introduces the Visual Basic for Applications programming language, covers creating subroutines and functions to hold code, and provides a solid grounding in the Excel 2007 object model.with office 2010, this does not appear to be an issue. If it is not maximised, when I press f2, to edit a cell, i just hear the word "payne" and i'm not able to use the cursor to read what's in the cell." any thoughts? It looks like Excel becomes massively slow when maximized, if the worksheet also contains one or more comments.sometimes there is no speech at all when moving between cells, particularly if i have entered something into a cell and then hit enter to update it. When I maximise the window, this is when excel goes incredibly slow and I am seeing a 3 or 4 second lag. It seems that all calls to properties on an Excel range object become 3 to 4 times slower in this situation.The slowdown is only on the sheet with the comment, but it seems to be the same anywhere on that sheet.I tried with a couple of older versions of NVDA, and it seems to be something that was introduced in NVDA 2015.2.