Custom reports would be considered out of scope of support for Sage 300 support. A partner that has worked with custom reports may be able to reply.

Change the properties of the parameter used for cut off date.  It appears that "Allow range values" is set to True; it should be False.  Discrete value should be set to True.

After opening the report in the Crystal Designer, open the Field Explorer, then under Parameter Fields locate the parameter in use for that field.  It is probably something like CUTOFFBY.  Double click on that parameter to edit it.  In the Value Options section, you will see the properties for that parameter.  The discrete and range value options should be drop-down True or False.  Click on that word to select the other option.  Click OK, then Save the report.  That should do it.

Below is a typical example.

Since this works for other users, I would guess this issue is being caused by screen resolution or use on a second monitor.  Either way, I would suggest increasing the width of the vb form you are using.

Agreed with Jim.  I used to write my original reports using separate FROM and TO fields.  it's far easier to use a single parameter that allow a RANGE input.  Of course then you need to modify the record selection to be in the format of {Date} in [DateRange].   it also allows multiple ranges so could use Jan and Feb of 2024 plus Jan and Feb of 2025 for example. 

Shane's note below about dual monitors is also a possibility as I know strange things happen if you don't have identical resolution on both.

Right.  Check to be sure that the scale in Windows display settings is set to 100% on that workstation.  Some people like to set their display scale higher, and Sage does not play well with that.

Thank you all for your replies.

At first I also had a feeling it was a graphics rendering issue, so I disconnected the laptop from the docking station and the multiple monitors to have only a native display. I tested different scaling options in Windows, I even modified the RDP remoteapp file by including:

disable dynamic resolution:i:1

desktopwidth:i:1920

desktopwidth:i:1080

in order to force native resolution but without success. Also, comparing with another user, I realize that when opening the same report, the form opens correctly (with both fields) but in addition, it seems to open in a kind of Crystal Reports editor (see attached screenshot), whereas in the case of the affected user, only a standard Sage window opens.

This might just be a configuration issue related to the Sage profile itself or some kind of file association? The person who usually manages Sage is on maternity leave, and she's the one who assigns rights to new users, while I, as the IT manager, only handle the Active Directory/RDP side.

Yesterday I tried to open the .RPT report in order to give a try on your solution, but realise that the custom report edit tool (Info-Explorer) that we have don't have active licence even if we pay for it, so the consultant that sells us thoses licences including Sage will call me today to fix it. He should be able to shed some light on all this btw.

I'll keep you updated.

Thanks again.

See if they are running the same report?  maybe same name but from different folder.  Sage has built in SAP report viewer now, so not sure how it could open in a different application?