As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
I have a field which I use in my report it has as fieldtype: A16
But when I run the report it gets shortened 2 only three characters. It has nothing to do with the column-size. It is just shortening it for no apparent reason.
Example.
If in SQL the field shows the following values: 00001256789 00002567456
It wil show in DS just 789 and 456.
Anyone familiar with this issue? I have searched the forum and the help file but with no succes.
Thanx in advance,
NordinThis message has been edited. Last edited by: Kerry,
7.7.03 OS is Windows 7 We create al sorts of outputs depending on the demand, HTML (most cases), Excel (some cases) and PDF (some cases)
Posts: 32 | Location: Utrecht, Holland | Registered: December 10, 2008
Could you show the definition of this field in the MASTER file? Could there be a DEFINE on the field with the same fieldname that takes the last 3 characters?
Daniel In Focus since 1982 wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006
No there is no define field used here. We have a policy that we don't temper with the masterfiles. If we want certain fields changed, we do it either in an SQL view or in the report itself.
Field that gives us a headache in the master file:
The data that you shows appears to be integer, yet the MFD says it's an A16. This leads me to suspect that the MFD is out of synch with the underlying SQL table.
Also, the FIELDTYPE=R raisses warning bells. FIELDTYPE=R is only applicable under a very narrow set of circumstances - typically when the underlying database column is an identity column.
If these thoughts do not help, suggest you turn on SQL tracing, then post that along with the full MFD & SQL table definition - mybe something will jump out at us.
Are you quite sure that there is no other masterfile with the same name on your system that gets used first? You can find that out by issuing the command 'WHENCE mastername MASTER' just before you would do your TABLE. It will then show you which master file will be used for the query so you can find out if it is the correct one.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
Otherwise, try to find out what sql is being sent to the DBMS and see if that's correct. Use the following commands in your fex to accomplish that:
-* Capture sql output
SET TRACEOFF=ALL
SET TRACEON=SQLAGGR//CLIENT
SET TRACEON=STMTRACE//CLIENT
SET TRACEON=STMTRACE/2/CLIENT
SET TRACESTAMP=OFF
SET TRACEUSER=ON
SET XRETRIEVAL=OFF
Hope this helps ...
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
"FOC2590 - AGGREGATION NOT DONE FOR THE FOLLOWING REASON: FOC2594 - AGGREGATION IS NOT APPLICABLE TO THE VERB USED SELECT TOP 100 T1."MSESSIEID", T1."SOURCETYPE", T1."MEET_DATUM", T1."MEET_TIJD", T1."AutoID", T1."PATIENTNR", T1."INPUTDATUM", T1."INPUTTIJD", T1."SOURCE_ID", T1."VALUETYPE", T1."METING_ID", T1."VALUES", T1."GEKOPP_ID", T2."KOPP_ID", T2."OBJECTID", T2."MSESSIEID", T2."PATIENTNR", T2."EERSTEDATU", T2."EERSTETIJD", T2."STATUS", T3."PLANNR" FROM EZis_Report.dbo.METINGEN_METINGEN T1, EZis_Report.dbo.METINGEN_MEETSESS T2, EZIS_Report.dbo.OPNAME_OPNAME T3 WHERE (T2."MSESSIEID" = T1."MSESSIEID") AND (T3."PLANNR" = T2."OBJECTID") AND (T1."VALUES" LIKE '%MUST%') AND (T2."KOPP_ID" = 'OPN'); 0 NUMBER OF RECORDS IN TABLE= 0 LINES= 0"
7.7.03 OS is Windows 7 We create al sorts of outputs depending on the demand, HTML (most cases), Excel (some cases) and PDF (some cases)
Posts: 32 | Location: Utrecht, Holland | Registered: December 10, 2008
A16 or A16V does not make any difference in retreiving data. But, I always like to make things as simple as possible in situations like this. So, the request apparently is a join of 3 tables. What I would like to see is what happens when you just access the one table that holds the problem field, so in this case a report that accesses only table METINGEN_MEETSESS. Just print the OBJECTID field, let's say 100 records. See if that's ok or not. Then take it from there and try to find what the problem is.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
Ok. Da's dan duidelijk. The join from the first to the second table is probably causing this. Check to see if PLANNR and OBJECTID have exactly the same format and size.
Think on it, both fields will have to have exactly the same format - and contents - to be able to do a join correctly. So if the formats are indeed exactly the same,check the contents of noth fields. It would not surprise me if they are indeed quite different, apart from the few that do match.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
Originally posted by GamP: Ok. Da's dan duidelijk. The join from the first to the second table is probably causing this. Check to see if PLANNR and OBJECTID have exactly the same format and size.
Think on it, both fields will have to have exactly the same format - and contents - to be able to do a join correctly. So if the formats are indeed exactly the same,check the contents of noth fields. It would not surprise me if they are indeed quite different, apart from the few that do match.
I am quite sure the join is fine see, my previous post August 29, 2012 11:07 AM.
7.7.03 OS is Windows 7 We create al sorts of outputs depending on the demand, HTML (most cases), Excel (some cases) and PDF (some cases)
Posts: 32 | Location: Utrecht, Holland | Registered: December 10, 2008
Syntactically the join may very well be ok. That does not mean it will work ok. Joining things is not a syntactical job, it's totally dependant on the formats of the fields and the data in them. These things will have to be exactly the same to allow the join to work correctly. Which is why I asked to look at the field definitions to make sure they are the same and to check the data in the individual tables to see if they match. Thusfar I have only read that reading from this one table only will produce the correct values. Now take the next steps - check formats and values in the other table.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
SELECT
TOP 100 T1."MSESSIEID",
T1."SOURCETYPE",
etc
FROM
EZis_Report.dbo.METINGEN_METINGEN T1,
EZis_Report.dbo.METINGEN_MEETSESS T2,
EZIS_Report.dbo.OPNAME_OPNAME T3
WHERE
etc
directly in SQL Server Management Studio do you get the correct results?
If the answer to that question is "Yes", then
2) Do you still have the FIELDTYPE=R, in the field definition for your MFD
If the answer to that question is "Yes", then remove the FIELDTYPE parm and try again.