The client claims that Studio 2017 is not compatible with Studio 2011, but this is not supported by the information on the SDL website. The translation memories should work just fine with 2011, and they *did*, until *something* happened in around July-August 2017. Since then, the memories either give an error right out, saying that the memory could not be opened because of the DateTime error, or they work for a while until a memory search runs into this kind of a string and gives an error message in the messages pane.

Yes, the client has the latest updates, and yes, I have the last version update for 2011 as well.

I have not found anything in my Web searches indicating that this is a widely occurring thing. I am running Windows 10 Home, and changing the locale/format etc. to English does not appear to have any effect compared to using the Finnish locale and format.

Anybody have any ideas? Is this a Windows thing, is this a runtime environment thing - should I update to Visual Studio 2017 runtime, or what have you?

I do realise that 2011 is no longer compatible with TM servers, but these are packages with the full memory included. If I get the memory as a TMX export, I can create a memory and import it just fine.

// JJ