Hi Mona,

What you describe is a feature that I would also like to have, but sadly, it's not available. The only way to choose which termbase a term is added to is by making that termbase first in the list, so no on-the-fly selection is possible. An alternative would be having your secondary termbase open in Multiterm and either manually entering the term there, or creating something like an Autohotkey script to do it.

If you happen to use Dragon, I have a command to do just that, which you can find here:

Adding Terms to a Secondary Termbase

Hi Paul,

I am not sure what exactly you mean by "... include additional attributes that reflect the reason for wanting to add in different termbases.  This way you can just change the attribute value whenever you add a term that doesn't reflect the default value.".

Would you mind explaining that a little bit more? 

Thanks in advance.

Regards,

Mona

Hi Mona,

I created a short video to explain what I mean.  Hope this explains the idea well enough.

Hi again, Mona,

As a follow-up to my suggestion to use AutoHotkey (which I'm by no means an expert on), I put together a blog post to explain and demonstrate how this works. You can find it here: Adding Terms to a Secondary Termbase with an AutoHotkey Script.

And here's a video demo:

Unknown said:

Adding Terms to a Secondary Termbase with an AutoHotkey Script.

That's pretty useful Nora... thanks for sharing.  I like AHK... brilliant little tool for many things and not just Studio/MultiTerm.

Hi Paul, I'm currently working a bit on Nora's script and thought it would be nifty to enhance it by using the MultiTerm SDK.

Since the documentation points to the possibility of using the SDK with VBA, I suppose it should be possible with AutoHotkey as well, but so far I haven't managed to get anything working yet.

Commands like Mt := ComObjCreate("MultiTermIX.Application") don't yield any results.

Any help would be greatly appreciated.

Kind regards,
Raphaël