Bug 92880 - CopyFromRecordset function not working since 4.x
Summary: CopyFromRecordset function not working since 4.x
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
4.0 all versions
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisectRequest, regression
Depends on:
Blocks: Database-Connectivity
  Show dependency treegraph
 
Reported: 2015-07-22 19:58 UTC by Jorge Albarenque
Modified: 2019-08-07 08:55 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
test file (8.68 KB, application/vnd.oasis.opendocument.spreadsheet)
2017-08-19 16:38 UTC, raal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jorge Albarenque 2015-07-22 19:58:54 UTC
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
Comment 1 MM 2015-07-22 22:01:44 UTC
How can we reproduce this bug ?
Comment 2 Jorge Albarenque 2015-07-26 03:21:17 UTC
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
Comment 3 Xisco FaulĂ­ 2017-01-31 00:01:46 UTC
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.
Comment 4 Jorge Albarenque 2017-02-20 13:15:31 UTC
Tested on v5.3.0.3, it fails with a NoSuchElement exception
Comment 5 Buovjaga 2017-03-04 17:19:15 UTC
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.
Comment 6 raal 2017-08-19 16:38:48 UTC
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?
Comment 7 Jorge Albarenque 2017-08-29 22:58:46 UTC
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
Comment 8 Buovjaga 2017-08-30 04:37:59 UTC
(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.
Comment 9 Buovjaga 2017-08-30 04:39:29 UTC
(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..
Comment 10 tommy27 2018-10-12 05:19:34 UTC
@Jorge Albarenque
please answer Buovjaga questions and tell if issue persists using latest LibO 6.1.2 release.

status --> NEEDINFO
Comment 11 Jorge Albarenque 2019-01-18 11:32:48 UTC
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
Comment 12 Buovjaga 2019-01-18 16:05:20 UTC
(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
Comment 13 Pokemon 2019-04-10 11:24:21 UTC Comment hidden (spam)
Comment 14 hipster-vintage-and-indie 2019-08-07 08:17:57 UTC Comment hidden (spam)
Comment 15 trackersphere 2019-08-07 08:32:48 UTC Comment hidden (spam)
Comment 16 mingmenhong 2019-08-07 08:45:12 UTC Comment hidden (spam)
Comment 17 health-news-blog 2019-08-07 08:55:44 UTC Comment hidden (spam)