I stand corrected. A reliable source has let me know that there should be no buffer overflow conditions with changing the size of the assignee group field within a Remedy form. I had assumed that the following define in ar.h:
#define AR_MAX_GROUPLIST_SIZE 255 was used in various struct declarations within arserverd to set character array bounds; but I am being informed that it is not. Thanks Doug. There are some other useful tidbits in the message as well so I am posting the reponse: "We have many customers who have extended this field (and the other dynamic group fields) to over 255 characters. All testing with 7.0 and later (and with 6.3 shows OK too) has shown no problem. There is nothing within the system that is tied to 255 characters. We work with the length of the field as defined. (in theory, things before 6.3 should be OK too, but I know of no testing that has been done on those earlier systems. But, nothing was changed to make it work in the later systems and it is fine there so it should be fine in earlier versions) 255 is selected as with ALL databases we support, this is an efficient field AND 255 is generally just fine (95+% of the time). If you are using a database where this field is not converted to a long/clob/blob/... when going over 255 characters, making it longer is fine. Having the field convert to a long/clob/ blob/... will make performance REALLY BAD so don't go over the length that is stored efficiently. There are no buffer overflows or issues with this field being longer. As x has found in his extension to 512 characters, it is working just fine. My guess is that he is either on a DB that supports efficient < 255 character fields OR the have only done small scale tests so the "long" issue is not affecting them yet due to small number of records in the form." Axton Grams _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
