• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 405
  • Last Modified:

TIBQuery.SQL does not understand "set term" command?

Hello :-)

I created quite a complex stored procedure which I want to execute dynamically using TIBQuery.
Within my stored procedure I use "SET TERM ^ ; " command.

The stored procedure is correct and works fine when executed from EMS.

When executed from TIBQuery it crashes with error message which mentions "TERM"

Thank you very much :-)

panJames
0
panJames
Asked:
panJames
  • 2
1 Solution
 
developmentguruPresidentCommented:
Show the SQL that you place in the TIBQuery to execute your stored procedure.  It should look something like:

Exec MyStoredProc

  I know that SET TERM can't be used everywhere.  If you are attempting to use the code of your stored procedure, verbatim, inside your TIBQuery then it likely will not work.  If you are calling the stored procedure correctly using your TIBQuery then The stored procedure would need to be looked in to.  In order to determine the problem it would help to see how it is called and the stored procedure itself.

  Without seeing any of that I can only say that you could fall back on some old fasioned debugging techniques.  You could use Binary Deconstruction on your stored procedure to see if something inside your procedure is causing the error.  Comment out half of it and see if the error still happens (last half).  If it does then comment out the last half of what is left, etc until the error does not happen.  If you are able to comment out all of the code and the error still happens then something must be wrong with how it is being called... perhaps a component update is needed... Until more testing is done (or more code shown) it will be difficult to be any more help.

Let me know.
0
 
panJamesAuthor Commented:
This is DDL query and starts this way:

SET TERM ^ ;
CREATE PROCEDURE ABC (

and it looks like TIBQuery does not like
"SET TERM"

panJames
0
 
panJamesAuthor Commented:
I think I solved this problem.

TIBQuery.ParamCheck := False;

and simple do not use 'SET TERM' at all.

Now it works fine.

panJames
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now