Bug 71264 - Macros: Macro apparently corrupt
Summary: Macros: Macro apparently corrupt
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
4.1.3.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-05 13:21 UTC by menes3llobis
Modified: 2013-11-05 20:19 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
files are highlighted in the instructions where it occurs the error "Object variable not set" (27.33 KB, application/pdf)
2013-11-05 13:21 UTC, menes3llobis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description menes3llobis 2013-11-05 13:21:42 UTC
Created attachment 88690 [details]
files are highlighted in the instructions where it occurs the error "Object variable not set"

Problem description:
 
Hello everyone
When it is called from Spreadsheet dialog box appears the error
"Object variable not set", sometimes on the properties of the control date and other times on the properties dialog box. A similar macro with the same properties on another spreadsheet does not give any problem, so I think it may be something corrupt in the file, but I can not figure out where as the other macros work.
Sorry if I made any mistakes in writing but I'm not master the English language.
thanks


Operating System: Windows 7
Version: 4.1.3.2 rc
Comment 1 Cor Nouws 2013-11-05 19:47:42 UTC
Hi there,

thanks for writing the issue and sorry that you have a problem with the macro's.
If the file is corrupt, pls make a new one :)
You may be helped with support from other users?
An overview of the possibilities can be found here
   http://it.libreoffice.org/supporto/

Since I do not expect a bug in the application, I close this as WorksForMe.
regards,
Cor
Comment 2 menes3llobis 2013-11-05 20:13:21 UTC
thanks for your prompt reply, but what about the file that contains the macro corrupt there are no problems, it is only when calling the macro that is the problem, then I think it's a problem when the program calls the macro
Comment 3 Cor Nouws 2013-11-05 20:19:07 UTC
yes of course. If after getting support from experienced users - lots of them in Italy - and there is a clear bug, pls reopen with a ODF file containing the macro.
Regards,
Cor