Regeneration failure - model is missing 1

[gaufridus]

I am new to ProE Wildfire 2 and have the following problem:
I can open an assembly located in one folder
I can insert a component (a screw from a family table) from another folder. This seems to work ok and the component is placed.
When I reopen the assembly at a later time/date, I get the following message:

Failed regeneration. Component model is missing. (referring to the screw from the other folder.

What am I doing wrong?
Do I have to place/copy the particular component in the same folder as the Assembly?
Do I have to place the generic part (and table) or just that instance in Assembly folder as well?

 

[cadcamguy]

check your search path

from config mentor

search_path
<directory pathnames>

Specifies a list of directories to search, in the order listed, for object or file retrieval. These directories, along with the current working directory and any directories specified in the search.pro file (see configuration-file option search_path_file) make up Pro/ENGINEER’s search path.

The directory path names can be relative or absolute. You can use special characters, such as ".." in UNIX and Windows (NT and 95), in specifying a relative path name.

Relative path names are initially resolved relative to the startup directory. If you subsequently reload the configuration file, the system re-evaluates the relative path names relative to the current (working) directory and appends the new directories (if any) to the search path (the previous path remains in place).

It is better, therefore, to specify the full path names always (in other words, from root) so as to avoid problems if you change working directories or use the same configuration file in another start-up directory.

The option can have several path names on a single line, separated by commas, semicolons or spaces. Whichever delimiter you choose to use, you must then use consistently. The option can appear any number of times in the configuration file, so it is not necessary to have more than one path name to a line. If objects with the same name are stored in more than one search-path directory, the system retrieves the first one that it finds, regardless of which object is the most recent.

Search paths may also include previously-defined environment variables. This is done by preceding the variable with $ in the search path definition. For example, the environment variable OBJ_TYPE can be used as follows:

search_path /partlib/$OBJ_TYPE/objs

When you are defining a search path in the Windows NT operating system, you must precede the backslash character with another formatting character.


search_path_file
pathname of <search.pro> file or pathname of its parent directory

Enables you to store in the specified directory a text file named search.pro, which contains a list of directory path names. These directories, along with the current working directory, and any directories specified by the configuration-file option search_path, make up Pro/ENGINEER’s search path.

In the search.pro file, you specify an individual directory path on each line, starting with the first line in the file. Blank lines and comment lines (which begin with !) are permitted.

You can specify either the path for the search.pro file or just the path to the directory containing that file. In the latter case, the system looks for search.pro in that directory. It is recommended that you use the full path name rather than a relative one, so as to avoid problems if you change working directories or use the same configuration file in another startup directory.

 

[gaufridus]

Thanks Cadcamguy, I must be brain dead today.
I had already put some folders in the search.pro and couldn't understand why some of that type of parts were being found but others (the recently created ones) were not.