【转帖】driveworks vs vba

yang686526

driveworks vs vba
are there any significant time savings or other advantages to using driveworks express as opposed to vba for design automation?
can complex algorithms be as easily coded into driveworks as in vba? more specifically, say an algorithm that would take 50 lines of code in vba.
is driveworks stable or does it crash a lot?
are programs easy to debug in driveworks?
thanks in advance
dmcallister
driveworks is not so much for "complex algorithms" as such.
the basic idea is if you have models that are similar and just require altering dimensions, configurations, swapping parts in assemblies etc to create the new models then dw is what you want. you do not really program algorithms or things like that into dw you pretty much select the dimensions you want to alter, features you want to suppress/unsuppress, and the likes, and use if statements or database lookups to determine the actions.
you design forms so that user can enter the new dimension data and info and away you go.
custom programming is for things that do not fall into this generic variation approach.
i work for a company that competes with driveworks. while driveworks is (like luke says) not for custom algorithms, our software could be used at such. it can be used for simple projects to very complicated projects...
we have a vb (visual basic) wrapper that makes custom algorithms much easier as part of the package.
check it out if you have time. here is the website...
the link didn't come through correctly. you can use the link under my name below. the application is called magix.
kevin bennett
kevinsbennett@navitech.us