Studio 2015, the most recent build, under Windows 7 with SP 1. Unable to integrate an .mdb file at all. I'm able to use it in MultiTerm, but not Studio 2015. The error message I get is: Value cannot be null. Parameter name: key

I am now working with Studio 2015, the most recent build, under Windows 7 with Service Pack 1. I am unable to integrate an .mdb file at all. I'm able to use it in MultiTerm, but not Studio 2015. The error message I get is: Value cannot be null. Parameter name: key.  I used to get this same error with 2014, but was able to work around it by integrating the same file twice, and the second time it would always have a name, then uncheck the one with no name. But now in 2015 I'm not even shown this screen, it just automatically goes to this error message. As I only have a few days left with my trial license before switching away from 2014 altogether, I sure hope I can get this problem solved! Server-based terminology works just fine. My agency tech person said I should ask here as she has no more possible solutions for me.

  • Hi Ruth,

    The problem might be related to not having compatible versions of Multiterm and Studio. If you are using Studio 2015 then you need Multiterm 2015 and not 2014.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Hi Paul,

    Actually, I hadn't installed MultiTerm 2015 initially, but my own tech person suggested that, and so I did, but it made no difference.

    Something else to try?

    Thanks!
    Ruth
  • Maybe try renaming it as an SDLTB and then add it?

    Can you share the Termbase so I can try it?

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Well, it took longer to decide, but it gave me the very same error message. How do I attach the file? BTW, thanks for telling the TW list about this forum, I for one was not even aware of it.


    Ruth

  • Hi Ruth,

    I think you just linked to your file and didn't actually load it.  You need to load it up there first.  So first go into rich formatting when you reply:

    Then use this option to load the file:

    However, you can also email me the file if you don't want to share this publicly?  Just send it to pfilkin@sdl.com  I'm out for the day but can definitely have a look later on.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Hi Ruth,

    As we discussed the problem was related to one or more of the fields in your termbase definition not working as expected.  So we resolved it by exporting only the languages and none of the fields, as these were all empty anyway.  To do this we used the Glossary Converter from the SDL AppStore as shown in the video below.  One thing I forgot to add to the video was how to make sure the fields were always displayed so you could "ignore them".  This option is not set by default:

    Once you have this the process is straightforward and you can create your new termbase in one operation with this tool:

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub