This is a macro that demonstrates a problem with Application.Wait. It is from an unknown version of excel. When Application.Wait waitTime tries to execute it results in an error "invalid procedure call". Rem Attribute VBA_ModuleType=VBAModule Option VBASupport 1 Sub Deal() ' ' newHour = Hour(Now()) newMinute = Minute(Now()) newSecond = Second(Now()) + 1 waitTime = TimeSerial(newHour, newMinute, newSecond) Application.Wait waitTime End Sub
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Checked with LO 3.5.0 release. Macro in question responds "BASIC runtime error. '91' Object variable not set."
Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
We've switched to msoffice. Feel free to ignore the bug report.
The status of your reported issue has not changed from "NEW," meaning that it is currently active. Since bugs are often mistakenly corrected over time and merely never closed, it would be helpful to have the problem validated on a newer version than the one mentioned in the initial complaint: https://phrazle.co
Before the changes to Bugzilla on October 16, 2011, this Bug was discovered. starting right from NEW without ever being explicitly confirmed. The error is changed to NEEDINFO status for this reason. To move this error from NEEDINFO back to NEW, please check if the bug still exists with the release before 3.5.0 beta1 or beta2. https://doodlebaseball.io/