Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.

ProTip:

 

Code is generally much, much easier to write, edit and refactor if it is laid out for proper encapsulation, instead of all put under one function..

 

Seeing that many lines of code put into one function makes my head spin. Especially when trying to figure out what it actually does/how.

 

Ex:/// When setting autoname fails to set because it has issues finding the parameters, instead of putting the try/catch in EVERY case statement, rewrite it as a function that does the error checking and returns the proper results. Be mindful of whether you want to accomplish this via 

1) A Sub (or occasionally a function) using a input/return variable by reference

2) A Sub using global variables

3) A function.


--------------------------------------
Did you find this reply helpful ? If so please use the 'Accept as Solution' or 'Like' button below.

Justin K
Inventor 2018.2.3, Build 227 | Excel 2013+ VBA
ERP/CAD Communication | Custom Scripting
Machine Design | Process Optimization


iLogic/Inventor API: Autodesk Online Help | API Shortcut In Google Chrome | iLogic API Documentation
Vb.Net/VBA Programming: MSDN | Stackoverflow | Excel Object Model
Inventor API/VBA/Vb.Net Learning Resources: Forum Thread

Sample Solutions:Debugging in iLogic ( and Batch PDF Export Sample ) | API HasSaveCopyAs Issues |
BOM Export & Column Reorder | Reorient Skewed Part | Add Internal Profile Dogbones |
Run iLogic From VBA | Batch File Renaming| Continuous Pick/Rename Objects

Local Help: %PUBLIC%\Documents\Autodesk\Inventor 2018\Local Help

Ideas: Dockable/Customizable Property Browser | Section Line API/Thread Feature in Assembly/PartsList API Static Cells | Fourth BOM Type