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'm trying to run against SYBase tables using an ODBC connection in WebFOCUS 7.6
No matter what I try, the only way I get a returned result set is using A26 in the master to describe the ACTUAL and FORMAT and passing the whole string to an IF statement. It will not work in a WHERE or EDIT of the field or using a wildcard.
IF PHPERIOD EQ '2008-12-30 00:00:00.000';
Found this in the help and it works! The Data format of HYYMDs is not supported through the SQLODBC synonym for the Remedy ODBC driver. Change the FORMAT and ACTUAL in the .mas from HYYMDS to A26. this allows you to extract date and time stamp info from the tables.
That being said, it's not the friendliest solution for the users and buying the Sybase connection may not be an option, times are tough and money is tight.
Any other suggestions out there before I continue down this ugly path to fix this? Perhaps I'm missing something that I have not tried.
Thanks!This message has been edited. Last edited by: Carol Dobson,
WebFOCUS 7.6.6/TomCat/Win2k3
Posts: 428 | Location: Springfield, MA | Registered: May 07, 2003
hmmm do you mean if you change PHPERIOD/HYYMDS to PHPERIOD/A26 it works? 1)Are you willing to change the master? 2) does this work DEFINE FILE ... MYPHPERIOD/A26=PHPERIOD; ... what do you get populating that new field, if you just leave PHPERIOD/HYYMDS 3) What about writing a user-defined function I'll help you with it, if you answer 1 and 2. You could put it in the edasprof so users could DEFINE FILE ... MYDATE/YYMD = F_PHPER(PHPERIOD); which would be less painful. But we need to know exactly what the content of that field looks like in its native state.
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
I still haven't received the raw data yet, however, I did find out that the time stamp is always zeros. That being said, I was able to prompt for a friendly date, create a define to concatenate the timestamp and the define does gets passed across to SyBase and runs quickly. I think I have a solution!
Thanks Susannah for the offer, you really are the best! Have a good weekend.
WebFOCUS 7.6.6/TomCat/Win2k3
Posts: 428 | Location: Springfield, MA | Registered: May 07, 2003
What would happen if you put some defines in the master file to convert the database field to a good old plain yymd field? Would you then still receive unsupported errors when selecting on the defined field? If not, then you would have to do a little bit of coding for each field, but you'd be quite all right when that is done.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
Actually, my real code did not have the semicolon, but just for fun, I tried it with the semicolon and it works.
Good news though, we are looking at purchasing the adapter which will solve all my problems. I'm keeping my fingers crossed!
We opened a case, however, were were told: "The general rule of thumb is that if they have an adapter for a specific type of datasource, using the ODBC against that type of datasource in unsupported."
After I tried to come up with my own solution (and I tried everything under the sun) I turned to ya'll to see if there was anything I missed since there are a million ways to do things with FOCUS. I needed something that would pass the date proccessing over to the SQL because these tables are huge. I'll be very interested to see if there is any performance difference!
Thanks everyone!
WebFOCUS 7.6.6/TomCat/Win2k3
Posts: 428 | Location: Springfield, MA | Registered: May 07, 2003
It didn't work with a WHERE unfortunately but was OK with an IF, makes no sense! The SQL trace did not pass the date processing with the WHERE. We didn't want our business partners to have to code like that or change every report for every date field, they are more GUI oriented so it was better for us to buy the adapter.
But there goes my Summit funds!
WebFOCUS 7.6.6/TomCat/Win2k3
Posts: 428 | Location: Springfield, MA | Registered: May 07, 2003