https://bugs.documentfoundation.org/show_bug.cgi?id=151796

            Bug ID: 151796
           Summary: Microsoft Excel macro goes down a cell at end of Sub.
                    Libreoffice does not unless you modify the code
           Product: LibreOffice
           Version: 7.3.6.2 release
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: medium
         Component: Calc
          Assignee: [email protected]
          Reporter: [email protected]

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to