[IV 2011 to 2014] - VBA transfer

[gmassart]

Hello

I have developped some macros with IV 2011 and we will migrate to 2014 next month.

I wonder if my macros will continue to work properly or should I expect to work on them after the migration?

Mainly it consist on titleblock automatic filling.

Thank you for your advices!

[mslosar]

We're about to get 2014 shortly as well.

I've seen it posted before...this should be at least close 🙂

Apparently VBA in 2014 has changed to be based on .Net. whereas previously it was based on just VB (6 i think, not sure). As a result, you're code doesn't just port over. FWIW, the macros I had in 2010 'just worked' under 2013.

I've heard that migrating to 2014 is close to a re-write in some cases. I haven't done it myself yet, though, so take it with a grain of salt. I did move all my stuff to addins via .NET though which should make the transition fairly seemless from what I've read.

Try searching 2014 vba for more info. I thought there was a blog post on it but I can't find it at the moment.

[ekinsb]

The previous answer is incorrect.  VBA is not based on VB.Net.  There was a change in VBA for Inventor 2014 but it's that VBA is not 64-bit rather than 32-bit.  Almost all VBA code will continue to run as-is.  The areas where there tend to be problems is when your VBA code uses external libraries because they also now need to be 64-bit.  These tend to be exception though and for most people all of there macros will just continue to run.

If you decide to write an add-in at some point you'll likely use VB.Net for that and then you will find some differences between VBA and VB.Net, but if you're sticking with VBA macros for now it should be an easy transition to 2014.

[gmassart]

Everything is fine with the macro, just the DatePicker which is in fact 32bits and so can't be registered.