How to use local termbase within server based project?

I'm using Studio 2019 SR2 - 15.2.4.1693, but the problem was there in Studio 2017, too (I was hoping to get rid of this by updating):

I'm working on a server based project. The client has included three termbases. I want to add one of my local termbases, too, and have it sit on the first place so I can actually add terms to it (the client's termbases are read-only).

However, after moving my local termbase to the first spot in the list, it doesn't stay there. When I open the termbase configuration window, the local termbase is back on the last spot in the list.

As soon as I close the window and try to add a term, I'm told that I'm not permitted to write to the termbase (what's more, the window informing me of this keeps re-opening, so all I can do at this time is close Studio using the task manager).

So practically I can't use local termbases within a server project that already has a server based termbase attached to it.

Anything to be done?

Regards,

Erik

Parents Reply Children
  • Hello

    I tried to reproduce the issue in the described environment without success.

    The termbase order manually set in the Project Settings will not change, I can therefore add new terms to the local based termbase.

  • Hi Adrian,

    It's great to hear (and I somehow anticipated that answer due to prior experience), but unfortunately, it doesn't help. I still can't use local termbases, nor can other colleagues connected to the same GroupShare project.

    Regards,

    Erik

  • I'm attaching a screencast showing the error.

  • I'm bumping this just to let you know that the problem persists. I am able to have my local termbase activated as the standard termbase for some time, after which it is automatically moved to the bottom of the list, at which point Studio says that I have no permission to write to the termbase. At this point, I have to kill Studio using the task manager, as the error message reappears immediately after confirming it.

    I'd really like this to be solved - using a local termbase together with server based ones is still barely possible.