R&Q29_45S error running upgraded composite report

I have received the below error when running a composite report to PDF upgraded from WD28. The composite report has two sub-reports. The line of code that errors is the second line here:
iDestination(iGenericPDF, gsInvFileName)
iPrintReport(gsfile,dsInvoice_details, dsInvoice_Summary,dsInvoice_xxx_facility_id,pHeader,pDateFrom,pDateto)

Windev (64 bit) is running on Windows 11 (note the error log states Windows 10, and the dll's in the error log are both 32-bit). Both sets of DLLs exist in the appropriate folders.

This appears to be a bug, or possibly a conflict of DLL versions. The same data used with a "standard" upgraded report (ie no sub-reports) runs correctly in the same script.

Thanks for any comments.
Mike

Error message follows:

You called 'iPrintReport'.
An unexpected internal error occurred.

Call stack:
Click BTN_<clientname>_Debtors (WIN_Win_ReportDevelopment2.BTN_<clientname>_Debtors), line 302

Date: 30/01/2024 11:37:16
Project: 5 ProActive

Additional information:
Error code: 1020
Module: wd290vm.dll (01A290045s - 29.0.267.15)

Debugging information:
Module : wd290prn.dll(01A290045s - 29.0.128.1)
Adresse de base : 5E7B0000
Erreur systeme : Access violation (GPF)
EIP = 5E8E0E68
OS : Windows 10.0 (10.0.22631)

Registres :
EIP = 5E8E0E68 EBP = 007EE2F4
EAX = 00000000 EBX = 0BAEA660
ECX = 00000000 EDX = 642FDDA0
ESI = 0B326F50 EDI = 00000000

Pile des appels :
[wd290prn.dll (5E7B0000), 29.0.128.1, 01A290045s] 5E84E115 : ExternalTermLibrary() + 601427 bytes

[wd290prn.dll (5E7B0000), 29.0.128.1, 01A290045s] 5E84E115 : ExternalTermLibrary() + 601427 bytes (0x32ba7a8, 0x3320f20, 0xbad8528, 0xb4b7fe0)
[wd290prn.dll (5E7B0000), 29.0.128.1, 01A290045s] 5E84E115 : ExternalTermLibrary() + 680680 bytes (0x0, 0xbad8528, 0xb5b32d8, 0x480aeb0)
[wd290prn.dll (5E7B0000), 29.0.128.1, 01A290045s] 5E84E115 : ExternalTermLibrary() + 373113 bytes (0xb326f50, 0x1, 0xbaead70, 0x1)
[wd290prn.dll (5E7B0000), 29.0.128.1, 01A290045s] 5E84E115 : ExternalTermLibrary() + 373003 bytes (0x14ae5b1c, 0x0, 0xbad8528, 0x480aeb0)
[wd290prn.dll (5E7B0000), 29.0.128.1, 01A290045s] 5E7CF666 : Execution() + 253116 bytes (0x7ee500, 0x3321fe4, 0x0, 0x0)
[wd290prn.dll (5E7B0000), 29.0.128.1, 01A290045s] 5E7CF666 : Execution() + 251901 bytes (0x7ee500, 0x3321fe4, 0x480aed4, 0x1)
[wd290prn.dll (5E7B0000), 29.0.128.1, 01A290045s] 5E7B4D64 (0x7ee5f0, 0xbad8528, 0x7ee56c, 0x46aa6a8)
[wd290vm.dll (64250000), 29.0.267.15, 01A290045s] 64437250 : InfoVersionWeb() + 1019458 bytes (0x480aeb0, 0x7ee704, 0x7ee704, 0x149dfd50)
[wd290vm.dll (64250000), 29.0.267.15, 01A290045s] 64330280 : Execution() + 497974 bytes (0x480aeb0, 0x7ee704, 0x7ee890, 0x5e973ca8)
[wd290vm.dll (64250000), 29.0.267.15, 01A290045s] 64437250 : InfoVersionWeb() + 577852 bytes (0xc5e3b0, 0xc5652c, 0x7ee701, 0x46aa6a8)
[wd290vm.dll (64250000), 29.0.267.15, 01A290045s] 64437250 : InfoVersionWeb() + 1022046 bytes (0x149dfd50, 0x1, 0x0, 0x480aeb0)
[wd290vm.dll (64250000), 29.0.267.15, 01A290045s] 64437250 : InfoVersionWeb() + 1021913 bytes (0x14ae47fc, 0x4cbeaf6, 0x20, 0x14a3f2f0)
[wd290vm.dll (64250000), 29.0.267.15, 01A290045s] 6425A437 (0x10, 0x4cbeaf6, 0x10, 0x644ca206)
[wd290vm.dll (64250000), 29.0.267.15, 01A290045s] 64437250 : InfoVersionWeb() + 602019 bytes (0x14a3f2d0, 0x64690018, 0x7ee704, 0x7ee704)
[wd290vm.dll (64250000), 29.0.267.15, 01A290045s] 64437250 : InfoVersionWeb() + 602038 bytes (0xc55b2c, 0xc55b00, 0xc75eb8, 0x7ee828)
[wd290vm.dll (64250000), 29.0.267.15, 01A290045s] 64330280 : Execution() + 387083 bytes (0x9a0f340, 0x480aeb0, 0x7ee96c, 0xb22b6bc)
[wd290vm.dll (64250000), 29.0.267.15, 01A290045s] 64437250 : InfoVersionWeb() + 903179 bytes (0x0, 0x0, 0x0, 0x0)
Pile invalide

Fonction (21,0)
EIT_TYPE_WDFILE : <2>
EIT_IDCODE : <18>

Turns out it is a bug, PC Soft have sent me a link to replacement dlls, wdbrwdll and wdbrw64dll.

Hi Mark,
Do you know if the bug fix is included in the 61j update?

Regards
Steven Sitas

Hi Steven

The version they sent me was 29.0.249.14 in both files. I haven't upgraded to 61j yet.

Regards
Mike

Update: Upgraded to 61r, composite report still results in error, this time reading "data source cannot be initialised". Same code works on a simple report, however, I'm investigating how the calls to the sub-reports (within R&Q) should be constructed.