This config.pro option creates a .xpr on a family table part save. It speeds up retrieval of family tabled parts as it pulls model info info from the .xpr file not the generic part file providing open time and memory savings. It also saves the instance geometry simp rep info into the .xpr file so you can benefit from the geometry rep with family table instances.
Now this is what ptc claims and I'm just starting my testing, but I'm looking for any more input on this functionality and also how Ilink and PDM Link handle these .xpr's
Any input would be great!
Thanks
Steve