Skip to main content
A
Aaronm8714-Alexandrite
14-Alexandrite
November 15, 2016
Solved

Creo requesting checkout of parts on opening

  • November 15, 2016
  • 3 replies
  • 6438 views

We use Pro/Intralink to store our cad data and one of the annoyances that comes up all the time is being asked to check out models when opening. It appears to be random components/assembles within the models, but I have to then select from continue, checkout, or mark read only. Each of those presents it's own problems, but I'd like to understand why this happens. Does anyone have any ideas?


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
Best answer by StephenW

Can you attach the parts and assemblies?

Any reference from models to each other other than assembly constraints?

With everything open in Creo and looking at the global reference viewer, any dependencies?

3 replies

B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
November 15, 2016

The number 1 reason a file is considered modified when opened is it was last saved in an older version of the software. If you just moved to Creo3 and open an assembly that was last saved in Creo2, you will see that those Creo2 files are considered modified.

A
Aaronm8714-AlexandriteAuthor
14-Alexandrite
November 16, 2016

All models were generated in the same version of Creo.

C
ChrisHanna10-Marble
10-Marble
November 16, 2016

Two things to look at/for:

1. Circular references.  In your startup directory are there any *.crc files?  Removal of all circular references will make Check In and regeneration faster.

2. Use the Global Reference Viewer to investigate the references and dependencies.  This includes Relation references.

Hope this helps.

A
Aaronm8714-AlexandriteAuthor
14-Alexandrite
November 16, 2016

No .crc files exist in my startup directory.

What would I be looking for in terms of dependencies?

Model B is a subassembly of model A in this instance.

If I open up model A, it says that model B is read only and cannot be modified. If I unlock model B, then I have to select checkout, continue, read only before continuing. If I open model B, it asks the same thing and always puts a + at the end of the iteration as if I have changed something in the model. I'm sure it has something to do with my workflow, but I'm not sure what to look for.

S
23-Emerald III
StephenW23-Emerald IIIAnswer
23-Emerald III
November 16, 2016

Can you attach the parts and assemblies?

Any reference from models to each other other than assembly constraints?

With everything open in Creo and looking at the global reference viewer, any dependencies?

A
Aaronm8714-AlexandriteAuthor
14-Alexandrite
November 16, 2016

Unfortunately I cannot upload any of these components.

Okay, so when I looked at the reference viewer under dependencies I saw several objects with a big X next to the name (they were suppressed objects). I also found one components with a dependency (had a trash can icon next to it). That seems to have fixed it, thanks!

So I guess the next question is - what causes dependencies? I didn't see anything in the model that was referencing the parent assembly,

A
Aaronm8714-AlexandriteAuthor
14-Alexandrite
November 17, 2016

Here's the latest issue - I have a library part for a threaded insert which has all parts verified and was regenerated before check-in with no issues. I load up one assembly that uses the inserts and no issues. I load up another assembly and it is asking to check out all of the family table parts even though only 2-3 different ones are actually used in this particular assembly.

I typically just mark all the library parts read online to just avoid the issue, but I would like to get to the point where no conflicts pop up when I open assemblies.

Terms & ConditionsCookie settingsAccessibility statement