Robert,

<< That the parameter exists somwhere in the script, or in the step about to
be initialized? >>

The step (statement) about to be executed.  The TDBISAMQuery.Params property
is reset for each statement execution.

--
Tim Young
Elevate Software
www.elevatesoft.com

Roy,

<< My fallible memory says that OnGetParams is fired for each loop through
the query not each statement in the query, so effectively each time you call
..ExecSQL. >>

What's the difference between the two concepts ?

The TDBISAMQuery.Params property is reset for the execution of each
statement in a script.  You can call that each loop, or each statement, and
still be right.

--
Tim Young
Elevate Software
www.elevatesoft.com

Robert,

<< My question to Tim (which obviously I'm not phrasing very well) is: since
at least according to the documentation OnGetParams works as you say, gets
fired once for every execution of the query (not for each step of a script),
then ALWAYS setting params in OnGetParams - whether it is a multi step
script or not - should work. >>

No, this is not correct.  Where does the documentation say this ?

<< This works if foo and fee are parameters in the first (or only) SQL
statement. Apparently, if we move the query.parambyname statements to
OnGetParams it will work EVEN IF FOO AND FEE ARE ON DIFFERENT STEPS IN A
SCRIPT. >>

No, that is not correct.

--
Tim Young
Elevate Software
www.elevatesoft.com