Skip navigation
449 Views 10 Replies Latest reply: Mar 28, 2014 10:04 AM by FrankS.Schiavone RSS
FrankS.Schiavone Platinum 1,377 posts since
Sep 8, 2011
Currently Being Moderated

Jun 18, 2013 11:04 AM

More lost data, more crashes.  The hits just keep coming.......

Lost a couple days work.  Yay.  Have had to reboot the system probably 15 tims or more in the last 1-1/2 days.  It turns out Windburn handles family table very poorly, especially when trying to copy them in the workspace.  I copied the family table assembly, carefully renaming the instances so there wasn't any issue.  Then I deleted the entire family table.  That worked, but then when I wanted to delete the instances from the workspace, the HAL 9000 system told me I had to delete the generic.  The system failed to either delete the instances from the Workspace (best solution) or even break the link between the files.  So, again, I'm having to go outside the system to back up the assembly to a network drive, delete the entire family table, then bring it into the workspace.


Excuse me, but would it be too much to ask to have the system we paid a TON of money for, actually work as advertised so I don't have to keep using a network drive to get the job done?  SRSLY?????

  • ptc-1288854 Gold 159 posts since
    Jan 19, 2007

    One of the BIG issues that we learned about, which is undocumented, is that Windchill cannot handle any family tables that contain asterixs.  It floored me that this essential, time saving tool was omitted from Windchill functionality.  We've since had to go back through our thousands of family tables to make sure all of the asterixs were converted to values, and we have to constantly remind users that this convenient functionality cannot be used in Pro/E.  If you're running into corrupted family table files on Windchill-Pro/E transfers, check the tables for asterixs.

  • ptc-124469 Copper 14 posts since
    Sep 20, 2007

    Deleting instances is cumbersome, but this should work:

         -  Open the generic

         -  Open all the instances

         -  Return to the Generic, delete the family table

         -  Save the generic.  You should see a message stating the instances are no longer table driven

         -  Save each of the instances that are currently in session


    This process will make the instances stand-alone so they can be deleted.

  • ptc-4900122 Copper 7 posts since
    Jan 24, 2013

    I know this is just about a year old, we identified this same issue, little sad if you ask me that PTC makes Creo so dependant on windchill and makes Creo work so well with family tables but yet windchill cant deal with family tables properly.....


    however we did find a solution, we have been working with a developer for a differerent issue and they provided us with a Library wizard tool that takes family table parts and strips the generics out and checks the generics into windchill.  Best solution to the problem so far, is the developer's website, program we have been using is Control's pro studio.  I would email them for a demo

More Like This

  • Retrieving data ...

Bookmarked By (1)


  • Correct Answers - 3 points
  • Helpful Answers - 1 points