Versioning issue in TD 3.0

Discussion forum about all things Report Builder (all versions).
satyajit87

Versioning issue in TD 3.0

Post by satyajit87 » 08 Dec 2010, 15:25

Hi,

I am using TD 3.0 and Windows Server 2003 os for development activities. There is a .qrp report in which a field called "description" (Datatype :-Char[255]) is accessed from database and displayed. But after an upgradation of the operating system to Windows Vista the values are not getting displayed in the report (the field in the report simply remains blank).

eg:- substr(bo.name,1,250)

When i change it to substr(bo.name,1,60) the values properly get displayed in the report but beyond that size the same thing haapens again. Using CONCAT operator also has no impact on this.

Could anybody advise on this.

Regards,
Satyajit

Jeff Luther

Re: Versioning issue in TD 3.0

Post by Jeff Luther » 09 Dec 2010, 23:42

QRP file is in the DB? Did anyone ever update (read in, check and save out) the QRP in Vista? v3.x doesn't support that OS, but maybe it is a 'refresh' issue??

satyajit87

Re: Versioning issue in TD 3.0

Post by satyajit87 » 13 Dec 2010, 10:49

The QRP file is not in the DB. Rather the application accesses it to print some fields which are indeed present in the DB. This is not the case only for reports, there are a few combo boxes for which I am facing the same issue.

In vista OS the data in the combobox is getting populated but it's nt being displayed.

Could you put some light on this. And also please let me know whether this issue is only for 3.X versions of Gupta TD or it remains for the subsequent versions also.

Thanks in advance.

Cheers.

Jeff Luther

Re: Versioning issue in TD 3.0

Post by Jeff Luther » 14 Dec 2010, 02:51

In vista OS the data in the combobox is getting populated but it's nt being displayed.

Oh..., that may be the problem. v3 vs. Vista... Are you certain the values coming back from the DB are valid?

You might try a call like SalUpdateWindow(), SalInvalidateWindow() after populating to force a repaint of the CMB. Does the CMB display the values in a simple test case where you stuff a few value in with List Initialization?

satyajit87

Re: Versioning issue in TD 3.0

Post by satyajit87 » 14 Dec 2010, 07:19

When I tried putting in a few characters of the same string ( which was originally disappeared ) using SUBSTR the CMB successfully displayed values.

For e.g. :- The original string was - substr(bo.name,1,250)

I reduced the sting length to 60 and tried the below string instead of the above one.

substr(bo.name,1,60)

What I found out was the CMB did not display strings having length greater than 63. Same is the case with the QRP report too.

Jeff Luther

Re: Versioning issue in TD 3.0

Post by Jeff Luther » 14 Dec 2010, 17:45

Where is SUBSTR coming from? Have you tested to see that SUBSTR is returning a valid string for 63 and above?

Try SalStrLeftX() and see what you get.

satyajit87

Re: Versioning issue in TD 3.0

Post by satyajit87 » 15 Dec 2010, 09:24

The SUBSTR func is used in the SQL query present in the class properties of the Combo box in order to fetch the values of that particaular field [ bo.name ] from the database.

I tried by restricting the string size to 63 and the values displayed in the CMB but strings having length more than that didn't display.

Return to “General Discussion”

Who is online

Users browsing this forum: No registered users and 0 guests