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
Dim rs As Object
Set rs = CreateObject("ADODB.Recordset")
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 v126.96.36.199, 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]
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..
please answer Buovjaga questions and tell if issue persists using latest LibO 6.1.2 release.
status --> NEEDINFO
Tested on LO 188.8.131.52 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: 184.108.40.206.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
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