Macro documentprojects

[Anonymous]

I'm having some new trouble with Inventor VBA. Every time I open a new part file Inventor is creating a new 'DocumentProject'. It then loses its connection to the ApplicationProject, which has all of my macros in it, so my macro buttons no longer work. I have to open Tools>Macros>change to the ApplicationProject and then select each macro and hit 'Run'. This just started recently. Anybody know why or how to have it default to looking at the ApplicationProject again. This is driving me nuts. I've attached a picture that might help illustrate what is going on too.

Thanks,

Nathan

PS - I'm using Autodesk Pro 2014

[Mark_Wigan]

hi, just quickly need to ask:

-where is your default vba path pointing to, in your tools > application options > files > default vba project (is it set correctly / missing etc)
-is it local or on network
ps- -there is / was (if i recall in 2014) a setting in your application options to load vba every time you open a new file or to not load each time... what are you set to at the moment? (and have you changed that setting recently?)

cheers.

[Anonymous]

Mark,

Thanks for the quick reply. My Default VBA projet path is C:\_Vault Workspace\Master Project\Default.ivb, which should be correct for me. It is a local copy of the file from Vault. And I don't think I've changed that setting recently, but honestlyI'm not really sure what setting it is your talking about and I haven't been able to find anything quite like that in application options so far. Do you have a screenshot that shows the setting you're referring to?

Thanks,

Nathan

[Mark_Wigan]

hi Nathan.

sorry for the delayed response.

   this shows the option (may not be related to this topic though)

http://knowledge.autodesk.com/support/inventor-products/troubleshooting/caas/sfdcarticles/sfdcarticl...

i forget, did you test this stuff on other computers to see whether or not is was repeatable elsewhere?

before or after the issue arises, can you see the api window quickly and easily from your inventor?

i am suspect that there is a registry issue or something else crazy like an imbedded macro in one of your templates or something?

ps- not that it would matter but just out of interest, i would also copy/ rename that vba file and point to the new one, reboot, test it.