"Karl " <firstname.lastname@example.org> wrote in message <email@example.com>... > I have a legacy script from a vendor that is p-coded - so it cannot be changed. > > It generates this same deprecation warning in 2013b, but now completely fails in 2014a. > > Is there a work-around to this issue? It is certainly caused by changes in the Matlab set/get call sequence for java objects. You can duplicate the error with the following commands: [snip]
You need to go back to your vendor and ask them to change the code, or keep using Matlab 13b.