Pavel Tsvetkov

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.

Pavel Tsvetkov

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.

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