Bug Hunting Session
Bug 52600 - Excel Visual Basic compatibility issue in LibreOffice Calc: Inserted Calc formula with Excel Visual Basic Code
Summary: Excel Visual Basic compatibility issue in LibreOffice Calc: Inserted Calc for...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.2.3.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Macro-VBA
  Show dependency treegraph
 
Reported: 2012-07-27 19:41 UTC by Tor24_1975314
Modified: 2018-07-03 14:19 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Excel test file with macro (38.00 KB, application/vnd.ms-excel)
2012-07-27 19:41 UTC, Tor24_1975314
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tor24_1975314 2012-07-27 19:41:34 UTC
Created attachment 64802 [details]
Excel test file with macro

Inserted formulas per Excel Visual Basic code are not converted with the right formula separator symbol on Windows systems with other regional settings.
Example Windows "Regional and Language Options": "German (Germany)" 
with Formula/List Separator ';' and Decimal Symbol ','

Example:
Create in Excel a macro with the following code, set up the Windows regional and language options to "German (Germany)" and try to run this macro inside LibreOffice Calc:

Sub Test_Insert_Formula()
    ' Preparing Test:
    Range("A1").FormulaR1C1 = "3"
    Range("C1").FormulaR1C1 = "4"
    Range("B1").Select

    ' Testing Excel VBA Code in Libre Office:
    Cells(1, 2).FormulaR1C1 = "=IF(RC[-1]>RC[1],""greater than"",""less than"")"
End Sub

If the system formula delimiter symbol is set to ";" it should be inserted: 
=IF(A1>C1;1;0)
instead of
=IF(A1>C1,1,0)
Comment 1 Tor24_1975314 2012-09-02 11:41:02 UTC
This bug occurs in version LibreOffice version 3.5.6 and 3.6.1
Comment 2 Tor24_1975314 2014-02-18 18:34:02 UTC
This bug was also reproduced in newer versions of LibreOffice! 

Tested with LibreOffice for Windows versions: 4.0.4.2, 4.1.4.2 and 4.2.0.4
Comment 3 Tor24_1975314 2014-05-04 14:36:15 UTC
This bug was reproduced also in LibreOffice Calc version 4.2.3.3 and 4.2.4.1 rc!
Comment 4 QA Administrators 2015-06-08 14:42:57 UTC Comment hidden (obsolete)
Comment 5 Tor24_1975314 2015-06-15 21:17:01 UTC
The problem still exists!

This bug was also reproduced in LibreOffice 4.4.3.2!
Comment 6 Tor24_1975314 2016-06-26 14:31:44 UTC
This problem still exists and was also reproduced in LibreOffice versions 4.4.7.2, 5.0.4.2, 5.1.1.3 and 5.1.4.2 for Windows.

(Test system: Windows 7 64-bit, Intel Core2Duo P8700 2.53 Ghz, 4 GB RAM, Java SE Runtime Environment build 1.6.0_24-b07)
Comment 7 Xisco Faulí 2017-06-08 09:18:11 UTC
You can't confirm your own bugs.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 8 Tor24_1975314 2017-11-05 20:21:23 UTC
Bug reproduced also with the newest version of LibreOffice 5.4.2 (version 5.4.2.2 for Windows)
Comment 9 QA Administrators 2018-05-30 16:40:04 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2018-07-03 14:19:39 UTC
Dear Bug Submitter,

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-20180703