I suppose one could fudge the cache and print back an error (and instructions as to how to use the backspace key) -- but if the app is used for rapid-fire multi-document creation, cached values may not clear when the new form loads (Mozz had a bit of a problem with that a while back). You could use a (cough) frameset if you were averse to doing an "include" via some sort of profile doc, yes, or you could redirect to a form that uses the query string to raise an error message (pass in a terse message, say &err=email, then look up the long version for display).
And the profiles are not incompatible with the subforms. A bit more effort, yes (well, more than a bit), but that's what you get when you turn off all of the features. (I had to say it, Jake -- the Devil's looking over my shoulder.)
I suppose one could fudge the cache and print back an error (and instructions as to how to use the backspace key) -- but if the app is used for rapid-fire multi-document creation, cached values may not clear when the new form loads (Mozz had a bit of a problem with that a while back). You could use a (cough) frameset if you were averse to doing an "include" via some sort of profile doc, yes, or you could redirect to a form that uses the query string to raise an error message (pass in a terse message, say &err=email, then look up the long version for display).
And the profiles are not incompatible with the subforms. A bit more effort, yes (well, more than a bit), but that's what you get when you turn off all of the features. (I had to say it, Jake -- the Devil's looking over my shoulder.)