Created attachment 104822 [details] Vlookup problem with array changes Dear Team, While doing dragging of vlook up using command, gets #NA result due to array change, Pls refer to screen shot, While dragging down the command vlook up from cell, array cell no. also changing to down,This leads incorrect result or #NA. Result will be correct, only if the array is constant. I know if we put "$" before array cell no. It will get constant and result will be ok, but this is not a defualt way. If we are doing vlook up in excel, we are able to select whole column by clicking the header. But Calc doesn't allow selecting whole column with one click. I know there are some other way to do vlookup correctly, but the proper way is above mentioned. Pls help to enable option to select array by one click for the whole column. This will help to switch to calc from excel easily. [I am a wide user of spreadsheet as well as LibeO calc, and I am trying to promote LibO in my location (kerala/india)mainly in corporate sector. the above vlook up problem take the users away from calc. So kindly treat this as important issue for ground level users. *Don't know any one pointed out the issue before/Or any other solution already have in calc* (I believe, only people choose FOSS if there is a chance for employment,employment will create only if FOSS has users)
Created attachment 104823 [details] Array issue in vlookup
Created attachment 104824 [details] Vlookup problem with array changes (Attachment in JPG)
Hi.. You're using early release (x.x.0) that should be used only for testing purpose. Please try again with latest stable release (currently 4.2.6.2) and reset user profile. Also provide reproducible steps since it's hard to understand with that screenshots. Then change status back to UNCONFIRMED
Dear Bug Submitter, 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 INVALID 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
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID 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 -- The LibreOffice QA Team This INVALID Message was generated on: 2015-05-06 Warm Regards, QA Team