Description: Microsoft Excel macro goes down a cell at end of Sub. Libreoffice does not unless you modify the code. Steps to Reproduce: 1. Write program using MS Excel 2. Run program in Libreoffice Calc 3. Notice that the next cell is not set at end of program. Actual Results: the active cell is not moved down by one cell. I have to modify code with a very simple workaround. Expected Results: My workaround works. Reproducible: Always User Profile Reset: No Additional Info: There is a trivial workaround. I would be happy to upload the file that I prepared. Here is the computer code that explains the trivial workaround, but also shows a possible bug. It is found in the module "Private Sub Worksheet_Change(ByVal Target As Range)" near the bottom. ' USE EITHER LINE MS_EXCEL_1 OR LINE LIBREOFFICE_1. ONLY ALLOW ONE TO RUN, NOT BOTH. ' MS_EXCEL_1 LINE ' BELOW LINE IS USED IN MICROSOFT EXCEL VERSION. ' Range(strCell_Being_Moved_To).Select ' THIS IS MS_EXCEL_1 LINE ' LIBREOFFICE_1 LINE ' BELOW LINE IS TO BE USED IN LIBREOFFICE VERSION. ActiveCell.Offset(1, 0).Select ' THIS IS LIBREOFFICE_1 LINE The problem is that the "MS_EXCEL_1" line works properly in Excel but not in Calc. I have to comment out the "MS_EXCEL_1" line and uncomment out the "LIBREOFFICE_1" line in order for the focus to go to the next line down. I am happy with the workaround that I created. Thanks
Created attachment 183306 [details] spreadsheet with example of results
Your test file is not working for me. When I type number in column A, nothing happens.
Lee: please explain how we are to test this. The file contains no binding to events. After copying a number from MASSIVE_BARCODE_EXPORT to PHYSICAL_INVENTORY, I tried to manually run the macro COPY_COUNT_OVER_TO_WORKSHEET_FOR_EXPORT, but I got: BASIC runtime error. '1' An exception occurred Type: com.sun.star.container.NoSuchElementException Message: at /usr/src/debug/libreoffice-fresh/libreoffice-7.5.0.3/sc/source/ui/unoobj/docuno.cxx:4021. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
Dear Lee, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Lee, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp