This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
I have been making the transition from Trados & SDLX 2006 (MultiTerm 7) to Trados Studio 2009 (MultiTerm 2009).
Theoretically, MultiTerm 2009 can "automatically" reopen MultiTerm termbases that were "packaged" by a previous version.
In my experience, this worked correctly for SOME of my termbases, but not all of them. (Some caused MT 2009 to crash under Vista – but not under XP, strangely. This may be a UAC problem, but not the same one cited in a recent thread.) ... See more
I have been making the transition from Trados & SDLX 2006 (MultiTerm 7) to Trados Studio 2009 (MultiTerm 2009).
Theoretically, MultiTerm 2009 can "automatically" reopen MultiTerm termbases that were "packaged" by a previous version.
In my experience, this worked correctly for SOME of my termbases, but not all of them. (Some caused MT 2009 to crash under Vista – but not under XP, strangely. This may be a UAC problem, but not the same one cited in a recent thread.)
My solution was to EXPORT the termbases, rather than PACKAGING them. This creates XML files. Then, in MultiTerm 2009, I created new termbases and IMPORTED the XML (I used "slow" import).
This worked perfectly for all of my termbases. Additionally, I noticed that the new termbases are thereby created with the .sdltb file extension, rather than .mdb. This may represent a new file format. I don't know what advantages it has over .mdb, but the icon is prettier!
In brief, my advice is: 1. Export your MT termbases (to XML files) before moving to a new version of MultiTerm. At worst, this is an unnecessary precaution. Better safe than sorry! 2. Optionally, import them rather than transitioning the old files automatically.
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Vito Smolej Germania Local time: 09:23 Membro (2004) Da Inglese a Sloveno + ...
SITE LOCALIZER
why sdltb extension?
Oct 4, 2009
The files are still pure-bred Microsoft Access data Bases. I would assume, changing the extension was meant as a side step away from mtb, so that customers do not accidentally (with a double click for instance) call up Access. Now, that sdltb extension is associated with MultiTerm (no way to do that with mtb) there's one conflict less to handle.
Regards
Vito
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Create your account in minutes, and start working! 3-month trial for agencies, and free for freelancers!
The system lets you keep client/vendor database, with contacts and rates, manage projects and assign jobs to vendors, issue invoices, track payments, store and manage project files, generate business reports on turnover profit per client/manager etc.
Manage your TMs and Terms ... and boost your translation business
Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.