Thanks for your reply, I don't know why I was not notified, as I want to acknowledge contributions to query.
Certainly you have a good point to use the form fields themselves to constrain input.
One thing to consider is whether adding yet more fields to a form is OK, especially as a form gets ever more complex in the effort to get the data desired,
and,
whether the form designer would to prefer to NOT encourage more data to handle.
Already form design has to consider separate fields for Last Name and First Name as well as 5 or 6 address fields, even when the data parts are not used separately as handling the zip 4/5 carrier route requires separate fields to get that right, or you got to allow for the hyphen, adn those that just HAVE TO enter two hyphens and then there are the spaces that seem to surround hyphens and copy n' paste which will pick up spaces and on and on.
So I thought that, in this case, having one field that allowed for certain non digits would be an useful exercise to add another tool to the box.
Thanks to all who have wrestled with this conumdrum, as it was less straighforward that I would have ever thought.
Mike
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
