If you have the PKT workbench you could use a reaction (as mentioned by catiajim) or you could also use a knowledge pattern. Knowledge pattern requires R16+, but reactions have been around for a while now.
The big advantage with the knowledge pattern over a reaction is that it will...
If you want to pattern at the feature level then you could use a Powercopy or a UDF.
These can be instantiated multiple times using either a script or using a Knowledge Pattern. Knowledge Pattern needs a PKT license from R16 or above. UDFs can be scripted in all versions of Catia and...
The company that I work for have developed a product for documenting and automating processes. Recently, we have developed an application for a customer that allows them to control Catia. For simple tasks like reading a spreadsheet and setting parameters in a model there is no real coding...
The best place to start would be by recording a macro in your Catia session as you change the parameters (Tools -> Macro -> Start Recording). That will generate some code that will get you started. You need to be careful though because the macro recorder does not always capture everything.
You...
Coin3D, OpenInventor, OpenGL, OpenCascade, ...
http://www.google.co.uk/search?q=3d+geometry+library
Or if you want to make things easier for yourself, avoid C++ and try something like:
Blender, Panda3D, ...
Even if they don't import from 3Dstudio directly, you can probably translate to the...
You could take a look at some of the different open-source ERP systems that are out there (for instance http://www.erp5.org/). Even if one doesn't do exactly what you want, it may be better than starting from scratch with in-house development.
Andy
I prefer to use late-binding with VB6 and Catia. Although it is supposed to run slower, you'll find that it is Catia that runs slow and you won't notice the difference between early-binding and late-binding. If these terms are new to you they are covered in the VB docs, so you should read up on...
Here are a few more suggestions that you may want to consider:
1) Move a core piece of functionality into a separate DLL and call that from VBA. This will make it harder for your competition to crack your code.
2) Big copyright notice on the spreadsheet and even more in the code. Slip in some...
Lets say that you have a part "A" and you publish the sketch (name = "Hole Points") containing the hole points along with some other geometry of interest (say a reference plane or datum point).
Parts 'B', 'C' and 'D' all have external reference links back to the published sketch in 'A'.
If you...
