On Fri, 23 Jan 2009 13:53:00 +0000
ariesk <> wrote:
> clearing the local CC
> folder (what shouldn't be a problem in my opinion, as CC parts are
I'm not 100% positive so I could be wrong, but I thought that if
Inventor found an existing CC part already on a users computer it just
used that copy instead of creating it from metadata or what ever it's
I could have sworn if a person who has never worked on an assembly
before which is in Vault and contained CC parts, and that person has
never created the particular CC parts that are within that assembly in
any other assembly, then when that person checks out said assembly with
CC parts from Vault, that Vault should be copying down the CC parts to
that users computer.
If the entire CC folder was deleted, Vault should be recreating the
folder structure as needed on that system when files are checked out.
That is correct, but not the problem. The issue is that with an empty local CC folder, the newly created CC part (or in effect that 'metadata') differs from the vaulted CC parts which ought to be up to date through the migration process... and all libraries (metadata) are 'updated' through the migration...right? So how come they're different?
On Fri, 23 Jan 2009 15:00:36 +0000
ariesk <> wrote:
> That is correct, but not the problem. The issue is that with an empty
> local CC folder, the newly created CC part (or in effect that
> 'metadata') differs from the vaulted CC parts which ought to be up to
> date through the migration process... and all libraries (metadata)
> are 'updated' through the migration...right? So how come they're
I think I can see the issue you are pointing out.
Libraries are installed with the newest version of Inventor, not
migrated I believe, but I understand how you are stating it. However
you have brought up an instance where it is possible for a newly
created CC part that may not/wont jive with a CC part that has been
migrated in Vault.
To be sure we are talking about the same things, we did move all our data to the 2009 server.
When I say "migrate", I mean updating the file format of parts and assemblies from version 2008 Inventor to 2009 Inventor (which we did not do).
Migration happens in the background when an individual file (2008 format) is opened in 2009.
Here is what I think is happening...
When using content center, new part files are created in the Vault if that particular part has never been used before.
We have no problem with previously unused components.
When inserting a 2008 format component, Inventor requires the file format to be migrated to 2009.
Migration requires the file to be checked out.
After a user migrates the component to 2009, that user can check the component back in to Vault and use it normally without check out.
We are having problems (check out required) if a users local copy is 2008 and the Vault copy is 2009. Still requires check out.
We are planning to migrate all the Vault content center components with Task Scheduler.
I am thinking we need to go through and purge or update local content on all workstations after this.
On Fri, 23 Jan 2009 19:23:44 +0000
kennedgy <> wrote:
> I am thinking we need to go through
> and purge or update local content on all workstations after this.
Good idea. If your users have all files checked into Vault (and they
do not have any models stored on their hard-drive which could contain
CC parts, either in or out of the working folder), you should be able to
just go in and delete the folder called en-US in their Content Center
Files (or what ever name it is) folder.
Doing it the way I described above, you might be able to avoid
migrating the Vault files with Task Scheduler - but you would still have
to check out CC parts on a as needed basis in order to get them up to
Regardless of which ever direction you want to go, it would be best to
go thru and get all the older versions of CC files off every bodies