TS2755 With the new IOS7 how do i tell which phone number my text messaging is being sent to? on the old system the number used to be highlighted, now nothing is highlighted and i have ended up sending texts to my friends international numbers instead ???

Question

With IOS7 I am finding it impossible to (a) tell which number I am texting, when my contacts have multiple phone numbers, i dont know wether it si their home , monile/cell or international number... How do i differnetiate or know which number it is, especially when they text me from abrioad and i replying ...its not very clear adn has cost me extra in international charges

Answer 1

Thanks Michael. Apologies for the slow reply I was away for a bit (holiday blitz at work and visiting family madness etc.etc.) back now, I set both options you requested to "never " and retried the CMS software with no change. 
I do have progress of a sort though, as a test I took a separate test PC and put a clean install of Win7 on and loaded up the CMS software (it worked perfectly) and then took the version of ole32.dll off that machine and put it onto the computer I had built
for her (using Linux) and...
got a new error code. Darn I was so sure I had found a clever solution this time lol.
Anyway now when the CMS fails it gives me a similar error but the offending module is "ntdll.dll" sooo... I tried taking the "working" version of ntdll.dll from the test box and moving it over (making sure to back up the existing ones
first so I could put them back if needed) to her new PC and the PC would not boot. 
It seems to want the original versions of a few Dynamic Link Libraries and if I could somehow give it those while not breaking Win7 it should theoretically work seeing as it no longer errors with ole32.dll. 
ntdll.dll however seems necessary for Win7 to boot.
So what I am wondering now is:
Is there some way to have both versions of the DLL file in the system32 folder (bypassing the "cannot have two files with the exact same name in the same folder" thing) or rename the original DLL's something else and somehow make the CMS look for
the new named versions so the system has the updated DLL's it needs to boot/run and the CMS has the old ones it wants to run or is there someway to have a self contained install of the CMS, say on a USB flash drive and give it it's own E:/windows/system32/needed
dll's  path to the files it needs? 
Willing to try any other options or settings you may have come up with as well.
Thanks again for your reply and my apologies for not answering sooner.