Description: Comment objects do not have a Parent property defined. It should be a Range object of the comment's associated cell. Without that, it is very difficult to do useful work. For instance iterating over ActiveSheet.Comments becomes useless, as you can't where the comments are or what cell contents each relates to. Same behavior on 5.2.5.1 and 5.3.0.3 Steps to Reproduce: 1. have a worksheet with one or more comments. 2. get a comment object - eg: comment = ActiveSheet.Comments(1) 3. MsgBox typeName(comment.Parent) Actual Results: "Nothing" Expected Results: "Range" Reproducible: Always User Profile Reset: No Additional Info: Further example: ActiveSheet.Comments(1).Parent.Parent.Name should return the name of the current Sheet. Looks like Range.Parent isn't wired up either. I must be doing this wrong. "Function CommentFrom(r As Range)" is trivial but "Sub ExtractAllCommentsToTheRight()" is impossible. User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
Hello Aaron, Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
It's not a bug with a document or my setup. There simply isn't a Parent property on comment objects, and there should be one. Are you looking for examples of why this should be? There are a ton of uses - http://dmcritchie.mvps.org/excel/ccomment.htm has a boatload. Here's a simple one: Sub DelComments() Dim cm As Comment Dim ws As Worksheet For Each ws In Worksheets ws.Activate For Each cm In ActiveSheet.Comments cm.Delete cm.Parent.AddComment Text:="Comment is deleted." Next cm Next ws End Sub (from https://www.mrexcel.com/forum/excel-questions/539902-visual-basic-applications-parent-comment.html) This fails because cm.Parent, which should be the parent cell Range object, is Nothing. You'll get this error on that line: BASIC runtime error. '91' Object variable not set. I'll make up a file with that script and a spreadsheet with a comment if you think need it.
Eike: what do you think?
Worksheet comment parent is nothing, Expecting a range object of associated cell with some processing https://aussiessayservices.com/myassignmenthelp-com-review/ data here. I don't want to let down any of the people because sometime those accounts are not well and no one take those objects where we are going to show.
https://enalo.in
Hello Aaron, Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Created attachment 176932 [details] spreadsheet showing bug
I can confirm this bug with this version Version: 7.2.3.2 (x64) / LibreOffice Community Build ID: d166454616c1632304285822f9c83ce2e660fd92 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded
Dear Aaron J. Peterson, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Aaron J. Peterson, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp