• State Suggested Answer
  • Replies 14 replies
  • Answers 2 answers
  • Subscribers 432 subscribers
  • Views 6009 views
  • Users 0 members are here
Options
Related

Dependencies file not founded

Jesus Duran

Dear Colleagues of gateway or translators,

I cannot export the translated files or even open the files to translate, yes I can open them but the trados ask me for browsing for a file, which I do no know where to find and what it is.

The error say dependencies files not founded.

Can anyone of you help me to solve this problem?, please Paul can you help me with this problem?

Thanks before hand.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0 in reply to Adrian Komiński
    Hi again Adrian,
    I have no problem with crashes unless I do something myself to cause them. The reason I don't get crashes is that I systematically turn OFF 'Match repair' as soon as I've opened each package. When I'm proofreading, I don't need fragment matching turned on. Here's where you do it:
    If you're not working with project settings, the above function can also be turned off via File>Options. As I'm sure you know, any setting made via File>Options (your Profile settings) will be overruled by the same setting in Project settings. Very useful when dealing with different clients who have different requirements.
    I also have the 'Fragment matches' window closed in the Editor view.

    Then I keep LookAhead turned off, via File>Options, (even when I'm translating) here:
    That speeds things up, as does having 'Enable verification of segment' unticked under 'After Confirming Segments Manually', as marked above.
    I also turn off other features that I don't need, depending on the task in hand. For example if I have a really huge file in any software (not just Studio) then I turn off OneDrive syncing until I've finished working on it. That makes a huge difference to speed and stability.
    Hope this helps!
    All the best,
    Ali Slight smile
  • 0 in reply to Alison Field

    Alison, thanks a lot for the elaborate description. I get occasional crashes in different situations, but they don't seem related to what you've brought up. The last crash, for instance, was after the "object reference not set to blah blah" thing that's been popping up on me since forever. But that's not the only thing, so let's just skip this issue altogether and focus on the OP, as I wouldn't want to be accused of hijacking the thread.
  • 0 in reply to Adrian Komiński

    OK, Adrian Slight smile

    In that case, if I had the 'dependencies file' message coming up on projects I'd created myself, I'd run a repair of Studio and MultiTerm.

    I do this with any software that is malfunctioning... For example, I ran a repair on Microsoft Office this morning because Excel has been misbehaving... If that doesn't work, I run a reset. It's the logical way to keep your software environment healthy.

    Enjoy the rest of your day! I will, I'm proofreading, my Favourite Thing ... or at least I should be heheh Wink

    All the best,

    Ali Slight smile
  • 0

    Hello Everyone in this discussion,

    I had a similar problem as shown on the image, which was popped up on opening the file for translation. It might have been caused by CCleaner or Avast Cleanup Premium as I was using both around the same time the problem appeared. Whatever the reason, as this seems to be a temporary file out of the project's directory, Studio should be able to rebuilt it (even if some recent unsaved data could be lost), I believe, and this is not suggested in the dialogue, nor it happens. I believe simple closing and reopening the project should help - I did not try this however.

    In my case I did not notice any other error (besides the error message), till now. I could continue translating and the Save target as function was working fine.

    I reinstalled both Studio and Multiterm, as suggested here, and the error persisted. Finally I followed the link posted here by , clicked YES at the error message dialogue and selected the source file in the project's directory where the Studio had copied the file from its original location when I was creating the project at the beginning of the work. This solved the problem, it seems.

    I hope the same will help in your case, , although it seems yours case is more serious.

    Radek