James Anthony Froude
Like so many of us, I'm guilty of ignoring instructions.
When I installed Autodesk Vault 2012, I used the same migration procedure I've used for the last few releases. Surely nothing could change, right?
Wrong! I used Vault quite happily for the first couple of days. Then I needed to use the Copy Design tool.
Poof! I get this new error I've never seen before.
|Hello. What's this?|
Projects? I need to set a default project? Since when?
I finally break down and read the directions. As your typical male. This is difficult for me. As a matter of fact, I may deny this at a later date.
Well, since the new version of Vault allowed us to enforce a default project! If I had read the directions, I would have learned that!
So what does the default project let us do? It allows us to choose a project that is going to run our Vault. It helps prevent us from having file associations get confused, as can happen when multiple project files exist in Vault, and makes sure all our users are on the the "same page" as it were.
It can be set in Tools>Administration>Vault Options
|Setting the Default Project at an administrative level|
Now that it's set, I like this tool. It helps me keep things more consistent, and predictable. But the first time I saw that error, it was unnerving indeed!
So what is the moral of the story! Read the directions! You'll avoid surprises!
Here's a video on my experiences with this particular function!