November 16, 2017 at 11:37 pm
Comments posted to this topic are about the item Adding custom messages
November 16, 2017 at 11:37 pm
Nice back-to-basics question, thanks Steve.
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
November 17, 2017 at 4:51 am
Took me some time to submit my answer as I was looking for a non-existent catch.
November 17, 2017 at 5:57 am
Nice basic question to end the week. Thanks, Steve.
November 17, 2017 at 9:36 am
It was interesting back to basics for me as I was working through an issue for a customer.
November 17, 2017 at 11:13 am
Interesting question. As the answer isn't documented (the documenttion doesn't sy which of teh two errors will be signalled when both are made in the one cll, as here) , and I couldn't recall ever having had an error when adding a message I tried setting up a suitable user and running the script just to see, and the result was the wrong answer. So I repeated the test, and this time it got got the right answer. that led me to quite a lot of messing around with different contexts for the call to be made in, but that led only to the conclusion that usually the invalid message-id was signalled but sometimes (very rarely) the other error (attempt with only serveradmin permission to create an message that would get written to the Windows application log if that error was ever raised) was signalled instead. I didn't spot anything that influenced which error was reported, just that the system seemed usually to prefer to sigal the messaage_id error when given the choice betwen that and the permission error.
Tom
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply