hi ya if i was picking ... i'd (blindly) choose *.dwg ... as the master input file fmt if i was writing the code .... the internal db will be my own extensible format ... read in any format .. and output in any format - did that methodology for cae ( edif, tegas, verilog, blah, blah... hundreds of um and tens terabytes of data for cpu simulations abnd probably hundreds of teraquads by now if you pick the "foo format as the standard" .. you're stuck with its restrictions ... if your db is customized for it and NOT extensible to add other functions, features, fields that is needed by the other formats and its NOT much extra work ... c ya alvin On 22 Aug 2003, Guy Edwards wrote: > On Fri, 2003-08-22 at 13:22, Sagar Behere wrote: > [snip] > > 4) do something else to modify those g-codes to obtain > > a proper tool path > > I know I sound like a stuck record but.... > > The EMC software is probably what you want from step 4 onwards. I don't > think it can create gcode but once you have gcode it can do everything > else. >