Tim,

From the scanning I've done, I agree in that it's an extension, which allows freedom to implement and in the way you want.

I would maybe suggest a note/clarification in the documentation/help file for the overloaded expression just to be a bit clearer on the ordering of parameters.

REPLACE(<StringExpression>, <StringExpression>, <StringExpression>)

changed to

REPLACE(<OldStringExpression>, <NewStringExpression>, <OriginStringExpression>)

This would help with understanding the order.  While it matches With/In version, there's nothing to say you hadn't "verbalized" the common version of REPLACE(<OriginStringExpression>, <OldStringExpression>, <NewStringExpression>).

Documentation has always been great and this is the first time I've hit something that didn't jive.

I actually wished the other major DBMS's would add With/In for crystal clarity of parameters.

Lance,

<< I would maybe suggest a note/clarification in the documentation/help file
for the overloaded expression just to be a bit clearer on the ordering of
parameters. >>

Good point, I'll see what I can do.

Thanks,

--
Tim Young
Elevate Software
www.elevatesoft.com