17 Does Pro/ENGINEER over write existing objects when saving
to disk? What does the object version number indicate?
Ans: Pro/ENGINEER will not overwrite existing objects while
saving to disk. Objects are saved to disk with an object version number after the
file extension. Pro/ENGINEER will create a new object file each time the object
is saved, monotonically increasing the version number each time.
The object version number indicates the number of times the
object has been stored. Objects are saved to disk with an object version number
after the file extension. Example: A part called valve.prt will be initially
written to disk as valve.prt.1. Subsequent storage of this object will result
in the files valve.prt.2. valve.prt.3, etc. If the directory is purged, the
object with the highest version will remain.
When a top-level object is retrieved (for example, an
assembly drawing), it always retrieves the most recent version of the assembly
and its parts. Therefore, the version of the drawing does not necessarily have
to have the same version number as the part or assembly. This will frequently
be the case when several different users are working on the same files.
This wouldn't cause a problem unless a user deletes or
redefines a feature that is used as a reference by some other object. For
example, if a feature is deleted from a part that is used for assembling
another component in an assembly, then that component will fail placement when
the assembly is retrieved, and must be redefined. Another example is when
planar surfaces are used to orient the model in a drawing view, and the feature
is then deleted or suppressed. This will result in the message, "model
geometry for drawing view is missing", and the view will revert to an
isometric orientation, and must be re-oriented (using the default datum planes
to orient the views whenever possible will help to prevent this).
The best method for avoiding these situations is to use a
database management product that will manage revision changes made to
parts/assemblies/drawings. Without a system like this, any user can change any
model, regardless of what other users are doing.
18 Does Pro/ENGINEER offer an auto-save function?
Auto-save functionality is not currently implemented in
Pro/ENGINEER. The "prompt_on_exit" config.pro option can be utilized
to prompt the user to save objects in session before exiting Pro/ENGINEER.
19 What happens if I run out of disk space while saving my
objects?
If available disk space is depleted during storage,
Pro/ENGINEER will issue the message: object name could not be saved: Check disk
space or write access. Error in storage. Check previous message (then press
Enter):"Pro/ENGINEER will not save any portion of the object to disk. Disk
space must be made available before the object can be saved.
20 What is the difference between File, Erase and File,
Delete?
File, Erase removes the object from workstation memory. The
object is not removed from disk. File, Delete removes either old versions or
all versions of the object and all associated objects from disk. It is
recommended to approach this menu selection with a great deal of caution.
Creating backup copies of Pro/ENGINEER objects is considered good practice and
can reduce the effect of accidental removal of data.
21 Why is the following message given: "PDM database
object must be renamed by Pro/PDM application"?
By default, Pro/ENGINEER will not allow Pro/PDM objects to
be renamed within Pro/ENGINEER. The config.pro option
"let_proe_rename_pdm_objects" set to "yes" will allow
Pro/ENGINEER to rename Pro/PDM objects.
Warning: Objects renamed in Pro/ENGINEER will be considered
new Pro/PDM objects when submitted back to a Pro/PDM database.
22 Why aren't part files saved when File, Save is selected
in Sketcher?
While in Sketcher, the File, Save functionality will save
the section to disk rather than the part file. This functionality allows
sections to be stored to disk for future use in feature creation. Section files
are saved to disk with a .sec file extension. Once Sketcher is exited by either
completing the feature creation or quitting, File, Save will save the part file
to disk.
23 How is family table instances stored to disk?
All family table instance information is stored within the
generic model.Pro/ENGINEER does not save a unique object file to disk for each
instance.
24 How can copies of a part be created?
Ans : The File, Save As functionality allows copies of part
files to be created using the following technique: Select File, Save As.
Pro/ENGINEER will open a Save As dialog box. The current object in memory will
be the default object to copy (in the Model Name section of the dialog). The
name of the new object is specified in the New Name line in the dialog.
25 Does Pro/ENGINEER save all components each time an
assembly is saved?
Ans : By default, Pro/ENGINEER does not store all assembly
components to disk upon each File, Save operation. Instead, Pro/ENGINEER will save
the assembly file and only components that have been modified. By setting the
config.pro option "save_objects", this can be changed. By using this
option, Pro/ENGINEER can be instructed to save all dependent objects, save only
the objects that were modified, or save modified objects and objects specified
by the user.