Choosing a renamed configuration

Now 2004 seems to have plateaued we are about to upgrade (still on 2001+)
But perhaps we should jump to 2005 if there is compelling benefit

We are in the process of deciding naming rules for configurations but
changing a configuration name causes the default config to be loaded.
So I am wondering if this issue has been resolved in 2004 or 2005

For example, this would seem an appropriate user interface:
"configuration not found, would you like to find it yourself?"
If that were so, then we could experiment with some name tweaks without
losing information.

 

I have seen this message before in SW2004 (or something very similar) when
opening assemblies.

"The configuration xxxx can not be found. If this configuration was
renamed, this assembly will use this newly renamed configuration."

To the best of my recollection, everything seemed to work fine. Although it
has been a few months since I have run into this, so I may be wrong.

 

Talk to your VAR about going strait from 2001+ to 2005 before you do it. I
believe they might advise against jumping 3 major releases for data
conversion reasons. Someone suggest to not jump more than 2 at a time,
though I am not quite sure who.

Corey