Bug 71072 - Other: VBA macro: ListFillRange not available
Summary: Other: VBA macro: ListFillRange not available
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-31 01:01 UTC by Jani Saarenpää
Modified: 2014-06-21 00:07 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
The example file descriped. (1.17 MB, application/vnd.ms-excel)
2013-10-31 01:01 UTC, Jani Saarenpää
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jani Saarenpää 2013-10-31 01:01:41 UTC
Created attachment 88387 [details]
The example file descriped.

Problem description: 
ListFillRange property not available in Libreoffice.

Example:
http://www.st.com/web/en/catalog/tools/PF257927
STSW-STM32091.zip => STM32F4xx_Clock_Configuration_V1.1.0.xls

Steps to reproduce:
1. Enable macros
2. Open the file described.
3. get bug 71071.
4. bypass this by changing the pointed line:
If (PLLUSB_table(i1, i2, i3) Like "1") Then
to 
If (PLLUSB_table(1, i1, i2, i3) Like "1") Then
5. Change the configuration mode to either "wizard" or "expert"
6. Get the error mentioned in current behaviour and a pointer to the line:
ComboBox15.ListFillRange = "$AL$19:$AL$26"

Current behavior:
"BASIC runtime error.
'423'
ListFillRange"
which is basically saying that:
"423 Property or method not found"

Expected behavior:
The property works as in the other popular office product:
"Returns or sets the worksheet range used to fill the specified list box. Setting this property destroys any existing list in the list box. Read/write String."
http://msdn.microsoft.com/en-us/library/office/aa175677%28v=office.11%29.aspx
Operating System: Ubuntu
Version: Inherited From OOo
Last worked in: 4.1.1.2 release
Comment 1 Joel Madero 2014-06-21 00:07:40 UTC
This is not a bug - we don't support VBA script. This is known and no need to keep this open to remind us of that. At some point maybe a developer will take on that task but we recommend using LibreOffice Basic or python.