Problem found and resolved. I tried tweaking the SSI file that modifies hidden fields to change the issue dispatching to my group and realized that it still had the same error on the same SQL statement. Obviously the file I changed was not the one included in the file! When I viewed the source I realized it was including an obsolete file.
A while back I put many of the config files under a different RCS repository. I was tweaking the one in the repository which should have been used via a symlink (a Unix shortcut, if you will.) Once I fixed the link to point to the file I really wanted, everything worked fine. At the heart of the problem was the fact that my HTML had two hidden fields with the same name. One set a value and one didn't. This is not good HTML coding practice! The new versions of the forms setup the hidden fields with no values set and then the SSI uses JavaScript to setup the values later on in the file. Now you know, what happens to your SQL statement when you try to use the values of two hidden fields with the same name. Arg! Thanks... now I need to research placeholders! --Chuck
