The answer or summary- spend lots of time reading the Intralink warning
dialog boxes, look for offending Generics/Instances, and Retrieve
Instances in the WS. Let the items get modified then update in the WS.
A File-Replace can also be done after retrieving instances, but then you
un-do your work that you are trying to save.
Not the end of the world if Intralink had the back-bone [front-bone] to
be able to support 1000s of objects in the Workspace, b/c then I'd just
include all instances to avoid the problem. A clear example of why a
Relationional database is superior to a I/O File Database. The local.ddb
file must be processed and sorted/searched/updated for simple
operations? i.e. Why not a local.ddb [or table] for each workspace? I
can see Intralink now, wanting to delete or add a record to the
local.ddb. Read in the complete File, Erase a few lines at the end of
the file, and re-write the entire file back to Disk. Perhaps this is
just done in Memory. Even then, bulky and poor implementation of an
otherwise decent and good product.
Thanks for the help - Robert Maillet
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.