{"id":7959,"date":"2016-11-18T09:00:03","date_gmt":"2016-11-18T14:00:03","guid":{"rendered":"https:\/\/blogs.mathworks.com\/pick\/?p=7959"},"modified":"2016-10-21T10:29:22","modified_gmt":"2016-10-21T14:29:22","slug":"matlab-file-association-fix","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/pick\/2016\/11\/18\/matlab-file-association-fix\/","title":{"rendered":"MATLAB File Association Fix"},"content":{"rendered":"
\n <\/p>\n

Sean<\/a>‘s pick this week is MATLAB File Association Fix<\/a> by Patrik Forssén<\/a>.\n <\/p>\n

<\/introduction><\/p>\n

Have you ever gone to open a MATLAB file of any kind and it did not open in MATLAB? The one I remember frequently from my
\n days in tech support was *.mat<\/i> files being opened in Microsoft Access because *.mat<\/i> is also a “Microsoft Access Table”. Seeing how there are almost 500 downloads in the last month, this seems to still be fairly common.\n <\/p>\n

Well if you run into this issue, Patrik’s file will fix it for you. It writes a Windows registry file with the file extensions
\n used by MATLAB associated with the release of MATLAB you run it in. It also provides instructions for backing up your old
\n registry file and then running the new one.\n <\/p>\n

<\/p>\n

One note is that there are two new file extensions:<\/p>\n

\n
    \n
  • *.mlx<\/i> for MATLAB Live Scripts<\/a>.\n <\/li>\n
  • *.mlapp<\/i> for MATLAB App Designer Apps<\/a>.\n <\/li>\n<\/ul><\/div>\n

    Comments<\/a><\/h3>\n

    Give it a try and let us know what you think here<\/a> or leave a comment<\/a> for Patrik.\n <\/p>\n