[WD20] "Report is too large" error! [solved]

Hi guys,

Up until now, I've always used HFSQL in Classic mode using the ordinary Windows file sharing. The customer concerned has now moved over to Windows Server 2012, so recently, I've installed and configured a test server with M$ Windows Server 2012 Essentials (trial version). I also installed and configured the HFSQL Control Centre on said server and Pete Halsted's blog post on the subject was very useful - cheers Pete!

I put the required (client/server) connection code into the Project Code section of my project and now my application connects to the server - huuurah!

BUT... there's a problem, an error has surfaced which I NEVER (ever) had running in Classic mode; whenever I run a report, I now get the following error:

Error at line 6 of Click WPB_OK process.
iPrintReport function called.
Page header of ReportProductOverStockCategoryActive report is too large: it cannot be printed.

----- Technical Information -----

Project : ObjectPos

WL call:
Process of 'Click WPB_OK' (WDWIN_PU_RPT_ProductOverStockCategory.WPB_OK), line 6, thread 0
'iPrintReport' function, syntax 0

What happened?
Page header of ReportProductOverStockCategoryActive report is too large: it cannot be printed.

Error code: 210044
Level: fatal error (EL_FATAL)

Dump of the error of 'WD200ETAT.DLL' module (20.0.148.6).
Identifier of detailed information (.err): 210044
Debugging information:
Fonction (21,0)
Additional Information:
EIT_CORRIGE_ETAT : ReportProductOverStockCategoryActive
EIT_PILEWL :
Click WPB_OK (WDWIN_PU_RPT_ProductOverStockCategory.WPB_OK), line 6
Click WPB_option14 (WDWIN_PU_Product_Reports_Menu.WPB_option14), line 1
Click WIMG_ProductOption9 (WDWIN_MainMenu.WIMG_ProductOption9), line 1
EIT_DATEHEURE : 06/02/2016 12:59:29

The preview window isn't displayed, although I think it flashes up so fast and is replaced by the standard error dialog.

Does anyone have a clue what might be happening here? Are there any settings I need to make in the Control Centre maybe? ...you know, something like the TABLESPACE settings you have in Oracle so that the report has enough system resources to be able to process, preview?

Any help and pointers here would be gratefully received - thanks...