Gabrielle Parnes wrote:
I tried everything and think at this point, I will just go with sacrificing the goat! It's a shame that they sell a product that from the start does not work,
Generally it works when you install it on a fresh system
But if you need some special software (in my case, a complete set ot .Net Frameworks for Passolo) or you have a very special configuration, it may be a bloody mess 'cause the more complex (i.e non standard) installation paths are not tested in SDL, I suppose.
E.g. if your .Net Framework 2 is patched before you install Trados/MT, the installation may be unusable (you should uninstall Trados/MT and .Net 2, disable the automatic updates in Windows, restart, install the unpatched .Net provided with Trados/MT, then reinstall MT/Trados...).
If you have MS Office Professional (i.e. Access), it may be some problems with the MS Jet configuration (very, very difficult to solve...).
The Java version is a well known problem.
As you see, the Multiterm-Trados combo is rather vulnerable and not very predictible but if you take in account the .Net and Java caveats, it should work... I hope...
but I've checked with my client and it seems that they rarely require the use of MultiTerm.
If the TMs aren't protected, the CAT hopping works as a charm for DVX
If anyone has any brilliant ideas, please let me know. Otherwise, I will be resigned to knowing that a product I purchased is utterly flawed. At this point, I think I need to put this aside, since I've lost too many hours trying to figure this one out.
DVX simply works
Can you give us a more detailed description of your system (e.g. Windows and Office version)?