Focal Point Banner


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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] Access database (FOC1400 error)

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] Access database (FOC1400 error)
 Login/Join
 
Luminita
Silver Member
posted
Hi,

Here is the code that I execute:

TABLE FILE ACC_PREDICTIONS
PRINT
MIN.BMA_LIBOR
BY WEEKS
WHERE ( UPDATE_TIME EQ '06/01/2005' );
END

and this is the error I get:
(FOC1400) SQLCODE IS -3030 (HEX: FFFFF42A)
: [22005] [Microsoft][ODBC Microsoft Access Driver] Data type mismatch in
: criteria expression.

If I comment out the WHERE line I get data. This is what I have in the master file for the UPDATE_TIME field:

FIELDNAME=UPDATE_TIME, ALIAS=UPDATE_TIME, USAGE=MDYY, ACTUAL=DATE,
MISSING=ON, $

If I just do:

TABLE FILE ACC_PREDICTIONS
PRINT
UPDATE_TIME
END

I get this:

UPDATE_TIME
09/27/2004
09/27/2004
09/27/2004
....

Has anyone seen this before? Any ideas?

This message has been edited. Last edited by: Kerry,


7.6.6 on AIX platform
Output: variety (Excel, HTML and PDF)
 
Posts: 33 | Location: New Hampshire | Registered: October 17, 2007Report This Post
GinnyJakes
Expert
posted Hide Post
Try taking the quotes and slashes out of your date literal to start. If that doesn't work, talk to someone who is doing straight sql into Access and find out the true date format and use that.


Ginny
---------------------------------
Prod: WF 7.7.01 Dev: WF 7.6.9-11
Admin, MRE,self-service; adapters: Teradata, DB2, Oracle, SQL Server, Essbase, ESRI, FlexEnable, Google
 
Posts: 2723 | Location: Ann Arbor, MI | Registered: April 05, 2006Report This Post
j.gross
Virtuoso
posted Hide Post
Capture the SQL and see how iWay is presenting the WHERE clause to Access.

Aside from any DATE field issue, PRINT and MIN. don't go together. Try is with SUM.


- Jack Gross
WF through 8.1.05
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
Darin Lee
Virtuoso
posted Hide Post
As Ginny infers in her remarks, there is a difference between what you see when printing a field (as determined by USAGE=) and what you should use in your selection criteria (as determined by ACTUAL=). You need to find out what the real format of the date is (20040927 or 2004-09-27 or 09-27-2004 or one of hundreds of variations) in the database and set the format in your selection criteria to match it.


Regards,

Darin


In FOCUS since 1991
WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex
Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex
WF Client: 77 on Linux w/Tomcat
 
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007Report This Post
Luminita
Silver Member
posted Hide Post
Hi all,
Thank you for your suggestions, I've tried everything and when I didn't know what else to do I asked some other people in our company for help. They opened a case with IBI and got a solution. The change we had to make was to add a SQL setting code to the edasprof of the sub server (in our case the Wintel reporting server). And now my dates are working fine.

Regards,
Luminita


7.6.6 on AIX platform
Output: variety (Excel, HTML and PDF)
 
Posts: 33 | Location: New Hampshire | Registered: October 17, 2007Report This Post
GinnyJakes
Expert
posted Hide Post
Can you tell us what the setting was and could you put [SOLVED] in the topic heading?

Thanks.


Ginny
---------------------------------
Prod: WF 7.7.01 Dev: WF 7.6.9-11
Admin, MRE,self-service; adapters: Teradata, DB2, Oracle, SQL Server, Essbase, ESRI, FlexEnable, Google
 
Posts: 2723 | Location: Ann Arbor, MI | Registered: April 05, 2006Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] Access database (FOC1400 error)

Copyright © 1996-2020 Information Builders