@TolpuddleSartre
I believed, at the time, I had given enough information.... I was unaware that what looks like perfectly reasonable and syntactically correct code can fail to work under "circumstances"
If someone had come back and said something like "The line of code looks fine. One case it won't work correctly is if "RemoteXY_CONF" is #defined as a macro. You may have done this yourself, but it could be in one of your included libraries, in which case you should address the matter to the library contributor"
That sort of reply would have shortened this thread dramatically, and I would have given up earlier, but to receive replies like (not yours, I will add) "The macro "RemoteXY_CONF" is invalid, fix it " doesn't cut it when I can't even see that it is a macro.
Now quit the derogatory remarks, please