Updating from IV2017 to 2018 - any API changes regarding VBA Macros?

[bshbsh]

Hey,

sorry for the stupid post, but a completely unexpected decision has been made and I am going to have to upgrade the entire company from IV2017 to IV2018. Tomorrow... Going in blind, without any testing, don't like it.

I guess the update will be fine, but I have some doubts if our Macros will keep on working fine. Are there any changes in the API that may break the macros? So far I read that modifying Library occurrences is no longer possible, I'll have to fix that for sure.

Anything else to look out for?

Thanks for any information.

[bradeneuropeArthur]

Normally spoken this will not be a huge problem because normally the API is added and not deleted.

But:

I was also having some problems in the past. 

So for sure you will run into some bigger or smaller problems.

Remarks:

Take the step now to learn programming add ins.

This will have more benefits and can be defined on any version of inventor.

At least for some versions back because you are able to use older SDK's

regards

[pball]

You already mentioned the library file access issue, which has a work around but the work around is apparently buggy and allows changes to library files from the graphical interface and not just the API. There is supposed to be a fix so the work around only works with the API.

I also found something in the pdf export code that I've been using that is from the help samples or the forum. The following line throws an error and simply has to be removed as it's no longer needed or valid in 2018.

If PDFAddin.HasSaveCopyAsOptions(oDataMedium, oContext, oOptions) Then

Other than that I've never had to make code changes from 2012 through 2018.

[bshbsh]

Thanks, that is useful info. We do use a macro for custom PDF creation.

I hope that's all. The library parts thing is my biggest concern so far.

[bshbsh]

Ok I have ran into this:

DrawingSettings.OfflineImageFidelity says "Application-defined or Object-defined error", so can't even read it. What's with that? the API help doesn't say anything about any changes.

[MechMachineMan]

---

@pball wrote:

You already mentioned the library file access issue, which has a work around but the work around is apparently buggy and allows changes to library files from the graphical interface and not just the API. There is supposed to be a fix so the work around only works with the API.

I also found something in the pdf export code that I've been using that is from the help samples or the forum. The following line throws an error and simply has to be removed as it's no longer needed or valid in 2018.

If PDFAddin.HasSaveCopyAsOptions(oDataMedium, oContext, oOptions) Then

Other than that I've never had to make code changes from 2012 through 2018.

---

Oddly with this one, it looks like they changed the first argument from the oDataMedium just to the document (or maybe it's always worked), so if you replace oDataMedium with the DOCUMENT object, it appears to work in 2018. The library files is a good mention too. Big perk of 2018.2 and on is the addition of global event triggers which is very nice, imo.

[bshbsh]

another thing: switching color schemes is still working, but it's now stupidly slow. (but it's not the API, it's stupid slow through the gui as well.)