[QUOTE="jon_banquer"] Replicated ??? Why would anyone want to settle for replication of what a source code language like Compact II has to offer ???[/QUOTE] Because: A. Very few Compact II programmers left out there. B. You want to move to an integrated design/manufacutering system because the origional Compact II product was dying long before it was Bravo and long before EDS bought them.[QUOTE] If a company wants to stay with writing Compact II and does not want to "replicate it with UG Manufacturing" can you tell me specifically how UG Manufacturing can do this without replication. ??? What if someone does not like the idea of replication, how does UG Manufacturing allow the same process of writing Compact II source that Applicon Bravo NCG does. Please be specific.[/QUOTE] First show me the piece of Compact II code that UG will not easily do. Mater of fact show me your CPII source code. [QUOTE] Have you considered that replication leaves a lot to be desired ala something like software emulation.[/QUOTE] Replication meaning "accomplishing the same task with the new software". Ex: redoing CPII engraving source code or probing functions into either a GRIP or UG/Open funtion. [QUOTE] If a companies policy was to edit Compact II source code on the shop floor instead of editing G code and then repost the edited Compact II source code can you specifically tell me how you can do this with UG Manufacturing ???[/QUOTE] The the company I worked for DID NOT ALLOW SHOP FLOOR EDITS except for minor feed and speed adjustments. The source never gets to the floor.[QUOTE] Looking forward your specific answers on this.[/QUOTE] Looking forward to some of your CompactII examples with descriptions.