Bug 123764 - FILEOPEN: Attempting to run scripts before document initialized
Summary: FILEOPEN: Attempting to run scripts before document initialized
Status: RESOLVED DUPLICATE of bug 123005
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.1.4.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-28 13:14 UTC by John W Cornell
Modified: 2023-11-29 11:03 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John W Cornell 2019-02-28 13:14:31 UTC
Description:
I receive the error "BASIC runtime error. Property or method not found: Sheets"
My sheet uses macros saved in "My Macros & Dialogs" and Libre is running the macros before "ThisComponent.Sheets" has any value. I work around this by repeatedly pressing OK until the spreadsheet is displayed, then I simply select reload from the menu and everything works fine.

Steps to Reproduce:
1.Create Macro in "My Macros & Dialogs" which references ThisComponent.Sheets
2.call macro from cell in spreadsheet
3.Save. Close Calc. Load sheet from FileManager.

Actual Results:
Error reproduced

Expected Results:
Error reproduced


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.1.4.2
Build ID: 1:6.1.4-0ubuntu0.18.10.1
CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: group threaded
Comment 1 Oliver Brinzing 2019-02-28 18:03:17 UTC
seems to be duplicate of:

FILEOPEN: Error on creating getCurrentController().getActiveSheet() for basic script from location=document ?
https://bugs.documentfoundation.org/show_bug.cgi?id=123005

*** This bug has been marked as a duplicate of bug 123005 ***
Comment 2 Mike Kaganski 2023-11-29 11:03:57 UTC
This issue is completely unclear.
Depending on specific details on the macro, it might be a dupe of bug 123005 (and NOTABUG, if it tries to reference objects that may legitimately be absent at some point when it's executed); or it might relate to bug 79588 comment 29 (only Standard and VBAProject libraries are auto-loaded); or it might be a valid issue of an object missing when it *should* be present...