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 email@example.com for further assistance. Reference the community FAQ to learn more about the community.
I have a problem where on one computer I can run a procedure in DevStudio that beings like
ENGINE SQLMSS SET CURSORS CLIENT SQL SQLMSS PREPARE SQLOUT FOR -DEFAULTH &te = '&te=' WITH CTE(AC, INTER, FEEDDIRECTION, FEEDFREQUENCY, etc etc etc
It runs beautifully
BUT THE Same procedure on my laptop will not run but both are using the same version of dev studio error is
FOC1400) SQLCODE IS 156 (HEX: 0000009C) XOPEN: 42000 : Microsoft OLE DB Provider for SQL Server:  Incorrect syntax near : the keyword 'WITH'.  Incorrect syntax near the keyword 'with'. If : this statement is a common table expression or an xmlnamespaces clause, : the previous statement must be terminated with a semicolon.  Sta : tement(s) could not be prepared.  Deferred prepare could not be comple : ted.
Any Ideas? Must be something very subtleThis message has been edited. Last edited by: Kerry,
Well, since I for one avoid using SQL in a WebFOCUS application like the plague for just this kind of problem(s), I would look at the versioning of the SQL Server data sources, the SQL Server Clients running on the two machines and last but not least the configuraton of the iWay connectors to make sure all of those match.
You might have to dig down as far as the SQL Server User Permissions for the User ID associated with the Data Server.
And before I get pilloried for my SQL statement above, if you think Roy is having fun, try working for an Oracle based client one month, a DB2 the next, take 3 months off and then help a client with both SQL Server and AS400. Trust me, "ANSI Standard SQL" is NOT standard :-)
Robert F. Bowley Jr. Owner TaRa Solutions, LLC
In WebFOCUS since 2001
Posts: 132 | Location: Gadsden, Al | Registered: July 22, 2005