Hi Geoff,

I am now basically finished with the new macro substitution features for
IBObjects but there is one issue still remaining:

Previously you had to specify the MacroBegin and MacroEnd tokens double in
your SQL statement such as:
SELECT %%MYCOLS%% FROM %%MYTABLE%%

However, you can now set the MacroBegin and MacroEnd tokens to strings
instead of Chars, for example:
MyScript.MacroBegin := '<**';
MyScript.MacroEnd := '--->';

If you previously used the default macro tokens '<' and '>', your SQL
statement would look like this:
SELECT <<MYCOLS>> FROM <<MYTABLE>>

Once my changes are released as part of IBO, the above SQL macro's will not
work anymore unless you specifically set MacroBegin to '<<' and MacroEnd to
'>>'. The reason for this is that the parsing routine will now specifically
look for what was specified as the MacroBegin and MacroEnd tokens. The old
method of parsing (i.e. double char's per token) will not work well in the
new context.

What are your views/opinion on this matter? (while Jason is at Borcon)

Best Regards,
Don Schoeman