Bug 81672 - Basic functions not recognized on loading XSLM file
Summary: Basic functions not recognized on loading XSLM file
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard: (target:4.2.6)
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-23 12:28 UTC by Bob
Modified: 2014-07-23 16:18 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Trivial spreadsheet in XLSM format, #NAME? on load (12.94 KB, application/vnd.ms-excel.sheet.macroEnabled.12)
2014-07-23 12:28 UTC, Bob
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bob 2014-07-23 12:28:29 UTC
Created attachment 103333 [details]
Trivial spreadsheet in XLSM format, #NAME? on load

When I open an excel XLSM file in LO 4.2.5.2 or OO 4.1.0 all references to functions written in VBA appear as #NAME?

If I open the macro source I can see all of the  functions are present and correct and if I make a dummy change to the spreadsheet formula they are then recognized and work correctly, eg Replace all = by =  

Requesting recalculation of the sheet is not sufficient to cause recognition.

Perhaps this is a timing window within file load, the check for valid function names is being made before the Basic environment has been fully loaded with macros.

It appears that 95% of the work to be able to read XLSM files has been done and it is a pity to have to resort to tricks to get macros recognized. 

The same spreadsheet in XLS format loads with problem
Comment 1 Bob 2014-07-23 13:01:55 UTC
Minor correction 
> The same spreadsheet in XLS format loads withOUT problem
Comment 2 Julien Nabet 2014-07-23 13:21:01 UTC
On pc Debian x86-64 with LO Debian package 4.2.5, I could reproduce the problem.

I don't reproduce this with 4.2 sources updated 15 days ago (and with 4.3 sources updated yesterday)

For the test, could you give a try to 4.2.6RC1 http://www.libreoffice.org/download/libreoffice-fresh/?version=4.2.6
If it doesn't work, you also give a try to future 4.2.7 with daily build (see http://dev-builds.libreoffice.org/daily/libreoffice-4-2/Win-x86@42/current/)
Comment 3 Bob 2014-07-23 16:16:58 UTC
I am happy to confirm problem no longer exists in 4.2.6.1 and for this bug to be closed
Comment 4 Julien Nabet 2014-07-23 16:18:58 UTC
Thank you Bob for your feedback.

I put this to WFM since there's no specific fix.