• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 190 subscribers
  • Views 1053 views
  • Users 0 members are here
Options
Related

Reorganizing a termbase opened in Multiterm, while the same termbase is also loaded in SDL MultiTerm 2019 Widget, will cause the termbase to grow 8 times in size

Pavel Tsvetkov

Hi All,

The name of this discussion topic says it all.

I have noticed that reorganizing a termbase opened in Multiterm, while the same termbase is also loaded in SDL MultiTerm 2019 Widget, will cause the termbase to grow 8 times in size: from 30 MB to 240 MB. At some point, the termbase will also stop to function.

It is fair to say that these two SDL tools are somehow incompatible under the above-described circumstances and will corrupt your termbase.

Thoughts?

Best regards,

Pavel Tsvetkov
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    I never noticed this before so I just spent a little time testing it.  Things I noticed:

    1. If the termbase is being used by the Widget it's now locked.  You'll see the MSAccess locked file because this is not intended to be used by two applications at the same time.

    2. There was no change at all in the size of my termbase and the process seemed to run through without a problem despite the lock file.

    I think the only thing I'd say is this.  Don't reorganise your termbase when it's being used by a different application.

    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

  • 0 in reply to Paul

    Hi Paul,

    Thank you for addressing this.

    The problem has occurred 3-4 times over the past 12 months but it was only the last time that I thought Widget might have been the culprit. The thing is that Widget has an autostart function and it is easy to forget that it is running in the background so reorganizing your termbase may occur when the two applications are using the same termbase.

    Maybe add a little check to Multiterm at the start of the reoranization feature to check that the same termbase is not opened in Widget? I understand that at this point you have not found any problems in the interaction between Widget and MultiTerm but frankly I can think of no other reason.

    Widget also needs a streamlining of the UI and functions that deserves a separate post.

    Best regards,

    Pavel Tsvetkov
Reply
  • 0 in reply to Paul

    Hi Paul,

    Thank you for addressing this.

    The problem has occurred 3-4 times over the past 12 months but it was only the last time that I thought Widget might have been the culprit. The thing is that Widget has an autostart function and it is easy to forget that it is running in the background so reorganizing your termbase may occur when the two applications are using the same termbase.

    Maybe add a little check to Multiterm at the start of the reoranization feature to check that the same termbase is not opened in Widget? I understand that at this point you have not found any problems in the interaction between Widget and MultiTerm but frankly I can think of no other reason.

    Widget also needs a streamlining of the UI and functions that deserves a separate post.

    Best regards,

    Pavel Tsvetkov
Children
No Data