<br><br><div class="gmail_quote">On Mon, May 25, 2009 at 6:46 AM, Jim Beuerle <span dir="ltr"><<a href="mailto:jbeuerle@elon.edu">jbeuerle@elon.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5"><br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><br>
> The problem comes when $fields['target'] is used in the FoxSetPW function. The {$$name2}<br>
> and {$$name1} are not evaluated from the form. The final result is another page named<br>
> Theadmin-Name2-Name1 with the correct EDIT id set.<br>
<br>
</div>I assume FoxSetPW is called as a Fox filter function.<br>
Fox processes any filter functions early, before variable substitutions.<br>
So in order to do field variable substitutions before, you nned to modify<br>
the filter function and add a line like this early in the function:<br>
<br>
FoxInputVarReplace($pagename, $fx);<br>
<br>
This assumes the filter function is using $pagename and $fx as variable<br>
names, otherwise change the names.<br>
<br>
The result would be that function FoxInputVarReplace is called twice,<br>
but that should do no harm.<br>
<br>
Hope this helps!<br>
<font color="#888888"><br>
~Hans<br>
<br>
</font></blockquote></div><br></div></div>THANKS! It worked great and now I understand a tiny bit more of the way FOX works.<br><font color="#888888">
<br>
Jim<br>
</font></blockquote></div><br><br>