• State Verified Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 432 subscribers
  • Views 2561 views
  • Users 0 members are here
Options
Related

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

Ruth Krawczyk

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.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    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

Reply
  • 0

    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

Children
No Data