In most cases you can use substitution variables instead. If you must use bind variables, you could use the OnCommand and/or AfterCommand event handlers to access the variables of the Query property.
Originally posted by Marco Kalter: In most cases you can use substitution variables instead. If you must use bind variables, you could use the OnCommand and/or AfterCommand event handlers to access the variables of the Query property.
Substitution variables are not always completely Ok (if I have to execute the same script many times they may cause unnecessary parsing, especially in multiuser environment). But your suggestion concernig Query property is very useful, I haven't noticed such possibility myself as Query belongs to OracleScript itself, not to the OracleCommand.
Note that all commands share the same TOracleQuery instance of the TOracleScript. This may cause the reparse operations you are trying to prevent by using bind variables.
Originally posted by Marco Kalter: Note that all commands share the same TOracleQuery instance of the TOracleScript. This may cause the reparse operations you are trying to prevent by using bind variables.