** This thread discusses the article: The API Corner: Reducing the Use of Compile-Time Arrays **
** This thread discusses the Content article: The API Corner: Reducing the Use of Compile-Time Arrays **
** This thread discusses the Content article: The API Corner: Reducing the Use of Compile-Time Arrays **
Hi Bruce
Interesting article. I use a similar technique of storing status codes, etc, in message descriptions, however I make the status code part of the message ID. For example all status codes might have a prefix of "STS" followed by digits or characters representing the type of status (or just filling in) and then the status code itself.
I tend to use numeric values for status codes, rather than "O" (Open), "C" (Closed), etc, so the message ID for Sales Orders would look something like:
All the best
Jonathan
** This thread discusses the Content article: The API Corner: Reducing the Use of Compile-Time Arrays **
** This thread discusses the Content article: The API Corner: Reducing the Use of Compile-Time Arrays **
Hi Bruce
Interesting article. I use a similar technique of storing status codes, etc, in message descriptions, however I make the status code part of the message ID. For example all status codes might have a prefix of "STS" followed by digits or characters representing the type of status (or just filling in) and then the status code itself.
I tend to use numeric values for status codes, rather than "O" (Open), "C" (Closed), etc, so the message ID for Sales Orders would look something like:
"STS" + "01" + "01" = STS0101 = Open
"STS" + "01" + "99" = STS0199 = Ready to Purge
etc
"STS" + "01" + "99" = STS0199 = Ready to Purge
etc
All the best
Jonathan