Dear List (David Easter are you listening),
<rant> I'd like to know how many of you out there have a size limit on a field named "Details" and/or "Description"? What is the "best practice" for a size limit on the "Details" field? In my mind, this field should be a 0-length (unlimited) field such that a person can input as many characters as it takes (within database constraints for a character field) to make a _detailed_ description of the problem. I can understand a limit on a "Summary" or "Brief Description" field for reporting purposes. Apparently the folks running the BMC Remedy Support site feel that 254 characters are sufficient for a _detailed_ description. Further, if you exceed this limit, do you get descriptive feedback as to why you couldn't save your ticket? NO. "Unable to setup data connection which is preventing this application from working correctly". What is that? </rant> Sorry to rant here, but after typing up a nice detailed description of a problem, I get an error message on trying to save my ticket. After butchering my response, I can finally save the ticket, but it now nowhere near reflects what I wanted to say and have to resort to several sequential ticket updates. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
