Diggity replied to Diggity's topic in Custom Web PublishingNote to self Figured it out. A. Fields are only validated if they are in fact modified. Unchecking the "Validate only if field is modified" option in the validation options of the database renders them un-validated to Web Companion. This is not true in the FileMaker client, which will continue to validate the field even if you do not modify it. This little tid-bit of information cost me the better part of a rainy Saturday (so who cares)... B. Handy way around this is to pre-populate the field on the HTML form with an innocuous 'space' character. Submitting the form will then *modify* the field; thus, invoking validation calculations. C. So as not to screw up the calculations with the once innocuous now troubling 'space' character, the validation calculations should have the following added in place of appropriate references to the field: Substitute( [FieldIWantToValidate], " ", "" ) TA-DA, and now off to view some porn.
Diggity posted a topic in Custom Web PublishingHi, I have been trying to validate that Field_B is not empty, but only if the value of Field_A has been set to "other." When I insert a calculation into Field_B's validation options in the database everything works as expected. The problem is that I cannot get Web Companion to return any error at all. At the moment I am using Filemaker 5.5 with WC 184.108.40.206 (Windows XP)