Spec references (delete & reload spec)

Everybody knows one should not delete a spec however has somebody created a utility to repoint the spref, when a spec is deleted and reloaded. The Marian PDMS Delta Load interface is pissing me off and I want to do the latter. Anybody done this succesfully?

VPRM has a similar problem. It does not delete the spec but removes it to limbo. When the spec re-runs the references get reset.
The problem is if a speco name changes (new commodity code) then the old one remains in limbo and the new one replaces it. This requires reselection of the component in design.
Neither system seems to be able to manage this problem. They need to track such changes and rename the old speco to the new name before the spec is run. This is how it is done when manually updating a spec.

Good to know somebody is sharing my pain :-) Any insomniac out their that has rippled the RESELECT command to pieces ($R110) and cast it into some code to have it run over a whole project without having to touch every component?

In addition has somebody come across some cases where the RESELECT command does not work? In other words is the RESELECT command bulletproof?

i have encountered redirection of components in my project before, i used excel vba to automatically track changes between old and new PMS.

but it is only limited to changes in itemcodes

Three (3) MARIAN RELATED SHOW STOPPERS have now been identified by us and Require manual intervention  before loading these  Marian Generated PDMS Piping specs.

[LIST]
Insert Doubles      => REMEDY  Open pipe spec and remove manually already existing entries in PDMS Cats & Specs DB
Incorrect Branch Tables     => REMEDY   Print Paper Piping Branch table and remove manually  undesired entries
Heading Errors                         => REMEDY   Manual Correct Heading
[/LIST]


Anybody wants to add to this list?

I would have thought that the branch tables needed to be correct in Marian before a transfer is made.
Shouldn't the headers also be output correctly from Marian?

Well, First of all the headers can be all over the place (pbore0, pbore1 &pbore3)

Secondly, Unlike for PDS, Marian does not export PDMS V12 Branch Tables and very likely coz of, lets say politically correct, time conscious :-) Marian Operators Olets get input on a range basis, i.e. 20" x 20", meaning also for equal bore components one gets a Olet Option. Meaning one Can place an Equal Tee as Well as an Olet. PS: As news broke, stocks in Olet Producing companies have gone up with 6,34% today :-)