The ADODB function CopyFromRecordset does not work, returns BASIC runtime error 423. Tried several LO versions, it works on latest 3.6 but is broken from the first 4.x onwards, so it must be some regression on the 4.x branch
How can we reproduce this bug ?
Sorry, I didn't include an example since any call to the function fails. Here's a very simple code to reproduce: ---- Rem Attribute VBA_ModuleType=VBAModule Option VBASupport 1 Sub Test() Dim rs As Object Set rs = CreateObject("ADODB.Recordset") Sheets("Sheet1").Range("A1").CopyFromRecordset rs End Sub
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.
Tested on v5.3.0.3, it fails with a NoSuchElement exception
With these types of reports requiring a special setup (ADODB in this case), it might be interesting, if the reporter could package a Docker image of the whole thing.
Created attachment 135662 [details] test file I get mentioned error in LO 6 after macro run. Version 3.3 without error. Is the test file sufficient?
I never understood why I was asked to provide a Docker image (of what??) for an issue that is so simple to reproduce: 1) Install latest version of LibreOffice in a Windows computer 2) Create VB macro with the mentioned code and run it 3) Watch the error message
(In reply to Jorge Albarenque from comment #7) > I never understood why I was asked to provide a Docker image (of what??) for > an issue that is so simple to reproduce: > > 1) Install latest version of LibreOffice in a Windows computer > 2) Create VB macro with the mentioned code and run it > 3) Watch the error message You skipped ADOdb setup for some reason.
(In reply to Buovjaga from comment #8) > (In reply to Jorge Albarenque from comment #7) > > I never understood why I was asked to provide a Docker image (of what??) for > > an issue that is so simple to reproduce: > > > > 1) Install latest version of LibreOffice in a Windows computer > > 2) Create VB macro with the mentioned code and run it > > 3) Watch the error message > > You skipped ADOdb setup for some reason. + this is the first time we hear you are running Windows..
@Jorge Albarenque please answer Buovjaga questions and tell if issue persists using latest LibO 6.1.2 release. status --> NEEDINFO
Tested on LO 6.1.4.2 Windows 10 x64. Issue still present. Buovjaga's questions do not apply since this is issue is about the Windows version. Macro code to reproduce is outlined in comment 2 of this ticket. status --> UNCONFIRMED
(In reply to raal from comment #6) > Created attachment 135662 [details] > test file > > I get mentioned error in LO 6 after macro run. Version 3.3 without error. Is > the test file sufficient? I also get the error Version: 6.3.0.0.alpha0+ (x64) Build ID: 62ce65fe042543e7aeaf83bf66f8c2357ff902c6 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-01-17_02:33:10 Locale: fi-FI (fi_FI); UI-Language: en-US Calc: threaded
Must be thanks for the nice post here you can follow here https://fixconnectionsbluetoothaudiodeviceswirelessdisplayswindows10.net and seen the fix connections for bluetooth audio devices and wireless displays in window.
i cherish perusing this article so beautiful!!great work! https://hipster-vintage-and-indie.com
So luck to come across your excellent blog. Your blog brings me a great deal of fun.. Good luck with the site. https://www.trackersphere.com
You made such an interesting piece to read, giving every subject enlightenment for us to gain knowledge. Thanks for sharing the such information with us to read this https://www.mingmenhong.com
I found that site very useful and this survey is very cirious, I've never seen a blog that require a survey for these actions, https://www.health-news-blog.com
Extraordinary substance material and awesome design. Your site merits the majority of the positive input it's been getting. https://www.healthtipstoday.net
You know your projects stand out of the herd. There is something special about them. It seems to me all of them are really brilliant! https://investconcept.net
Note that this can not be bibisected currently as we do not have repositories before 4.3. The bug appears in the oldest commit of the 4.3 repo.
https://newspostwall.com/today-deals/ https://newspostwall.com/cryptocurrency/ https://newspostwall.com/finance/
Thank you for unveiling such important information. https://attestationuae.com
https://www.certificateattestation.ae/
Dear Jorge Albarenque, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug