John Bartow
john at winhaven.net
Tue Oct 31 23:54:07 CST 2006
Hi Arthur, Good advice to help the user to prevent the error. What you can't see of course is a visual of the form, which was designed to replicate the paper FAX form the company uses. It has a text box large enough for slightly larger than an average "regarding" line on a FAX. While the text length for the field is set to 255, the form "visually encourages" one to only type so much. So, the user would normally not type more into the text box than it appears they have room for. The code I posted was the second level of protection, I doubt it ever gets triggered. :o) -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com Sent: Tuesday, October 31, 2006 10:17 PM Slick. My only criticism is that it waits for the user to go too far, rather than cautioning the user that he is about to go too far. (I tend toward guiding users to correctness rather than busting them for errors.) Perhaps your code could be modified to write the [length] + " of 255 characters allowed" to the status bar, so the user anticipates the error rather than commits it. Not a big deal. I like your solution. One of my mantras is, "Make the user feel like a dancer." That means preclude error to the best of my ability, and then of course deal with it should it occur. A.