Age old question - Validating a rich text field or manipulate text field on web to show appropriately (in R5.0.12)
Posted on 2006-05-04
Greetings learned colleagues,
I did a search but am still a little confused with how I should go about validating a rich text field. I've read that you should use a text field so why use a rich text field? Because the text field appears very small on the web, the words scroll off to the right and you cannot wrap. So (1) can I check that the rich text field is not empty using a computed text field that uses the value of the rich text field converted to text after a uidoc refresh in the querysave event or (2) how do I manipulate the text field on the web so that it shows up appropriately (it should look like you have the ability to type in a long sentence and wrap as well) and be able to carry out the validation as well. Anything entered in the Notes client should show up on the web and anything entered on the web should show up in the Notes client. The important thing here is that the validation check happens and that the field is not empty.
field, rich text, editable called explanation
field, text, computed with value of @Text(explanation) called explanation_DSP
test in querysave after the refresh (will the explanation_DSP field contain text or will the document have to be saved before the refresh will work?)
And since it looks like there are really 2 questions, I'm allocating the max number of points.
Thank you for your suggestions and help.