In the readme for Inventor 2014... I see this information:
Inventor 2014 removes support for VBA auto-run macros which are embedded in Inventor documents. These VBA macros are named: “AutoOpen”, “AutoNew”, “AutoSave”, “AutoClose” and “AutoEdit”. They can severely impact Inventor performance and pose a possible security risk. The suggested alternative to auto-run macros is to create an Inventor add-in.
I guess this is the reason that my macro (that uses Autosave) does not work any longer. This is a real deal breaker for 2014 for me. This macro is in EVERY idw that I create and it must work. It has been working since Inventor R4. The suggestion given is to create an Inventor Add-in. I dont have clue how to convert this to an Inventor add-in.
Any takers on converting it for me? Attached is the code.
Thanks
Solved! Go to Solution.
Solved by karthur1. Go to Solution.
what about running the code from ilogic?
If the commands you are using are not possible to rewrite in ilogic, it is possible to trigger a VB Macro to run from ilogic.
Using 'Event Triggers' you can set the rule to run upto creating a document.
Hi karthur1,
This tool might help:
I hope this helps.
Best of luck to you in all of your Inventor pursuits,
Curtis
http://inventortrenches.blogspot.com
Curtis,
No use since this will not work with an external iLogic code. I am looking at converting my code to an add-in.
Thanks
from my experience with the code injector, I am fairly sure that there is an option to keep rules as internal rules after running the injector.
I want to keep the the ilogic code as an external rule and the trigger should be set to "before save". I will need to experiment and see if I can get the code injector to do that.
I dont see an option for external rules in your screen capture.
I still have an issue with all my legacy idw files... all the way back from Inv 4. They are all in vault (1,000's of them). I would have to search for them, get latest from vault, check them out, run this code injector, then check them back in.... pray that there are not hickups along the way.
Hi Karthur1,
It's been several years now that we've encouraged developers to move away from those auto macros, mentionning that they will be removed at some point. Converting your VBA code to Vb.Net would be a matter of minutes.
We've been publishing numerous resources to help you achieve the migration VBA to .Net addins:
http://modthemachine.typepad.com/my_weblog/2008/10/converting-vba-auto-macros-to-an-add-in.html
http://download.autodesk.com/media/adn/VBA_Migration/DevTV_Recording/VBA_Migration.html
http://usa.autodesk.com/adsk/servlet/index?siteID=123112&id=770215
I hope it helps.
Best Regards,
Philippe.
Thanks Wayne Brill so converting this for me. Works great!!
You can find Waynes blog here about the addin that he wrote.
It is also attached here just in case the link gets broken in the future.
Can't find what you're looking for? Ask the community or share your knowledge.