I've just hit this error, which is apparently by design:
Connection Name may only contain alphanumeric characters, the underscore (_) and the hyphen (-).
I found this forum post, but was a bit depressed that connection names I've been using forever are now invalid... and as I've had to change one of them, I now need to change my entire naming system:
The character exclusion list may or may not vary by operating system and, more or less, will probably contain...
Can we reconsider a return to how it used to be for 4.0EA2? I use various constructs to ensure an appropriate message is carried with the connection everywhere it goes:
## WARNING ## - Production
Now I need to come up with a new naming system... <sigh>
Wait... it gets worse! I only just realized that the "@" is restricted. I have many different accounts on each database for testing purposes, so this means my standard of:
is now useless... so what, I start replacing a universally accepted naming standard with something random of my own design? Please, PLEASE at least let us use "@" in the Connection Name.
Thanks for the reply... and the workaround. It's rare that I edit my Service Names (obviously, or I would have hit this ages ago), so I'll just have to edit the XML by hand. Is there at least a bug/feature request somewhere in the system so that this can get worked on in the future? I'm sure I'm not the only person to be missing "@".