Actxserver no longer working correctly in R2018a, is there anything I can do to fix?
2 views (last 30 days)
Show older comments
I have a custom (written by someone else) .dll for dealing with a complicated binary file format. I am currently using R2016b and it works fine. My colleague has installed R2018a and it no longer works in the same way, preventing him from reading any files.
The code is as follows: h_file = actxserver('Rp66COMLib.CSlbDLISFile'); %Rp66ComLib is my DLL h_file.invoke(filename);
when I look at h_file on R2016b it is a Com object that has Interface objects that make sense when I look at h_file on R2018a it is a Com object that has an Interface object that seems random (Interface.942CFC0B_8F61_4F6B_83C9_60C8CB185ED7)
3 Comments
Steven Lord
on 25 Oct 2018
Define "no longer works in the same way."
Does it throw an error? If so, what is the full text (everything displayed in red) of the error messages your colleague receives?
Does it issue a warning? If so, what is the full text (everything in orange) of the warning messages?
Does it behave differently? If so, what is the nature of the difference in behavior? Different numbers in the results, different sized results, different typed results, etc.?
Does it do something else? If so, describe the behavior in more detail.
Are you using the exact same DLL in each MATLAB session?
Are you reading in the exact same file in each MATLAB session?
Answers (0)
See Also
Categories
Find more on Use COM Objects in MATLAB in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!