I will attempt to provide you with some help here.
First of all, this morning I saw a recall anouncement for Vaios in the news. Here is the link: http://www.foxnews.com/story/0,2933,416428,00.html. Check this before you start installing left and right only to find out you have to bring the box back.
Now to the actual issue at hand of moving projects from one computer to another. I will describe here one approach. There are others, but this is what I am recommending when computers are switched under the following assumptions: (Correct me if I am assuming wrong)
Across and the databases are installed on the same computer.
For each project, upon completion not only is the project exported but when exporting the project, there is also an export of at least the TUs for the particular project done (remember when exporting a project, CrossTank and CrossTerm Entries are NOT exported along with it).
First and foremost, EXPORT CrossTank and CrossTerm, I would recommend to not just transfer it to the new box but rather also make a copy on CD or DVD, just in case.
Here we go
Export CrossTank and CrossTerm.
Install the across version on the new Computer (Since you are installing 4.0, I would recommend directly also apply SP2C. I did this myself and I will send later on tonight a bit more detail on my testing) All in all, I am very pleased.
Since you spent the money on a new computer, you might want to consider (if possible) to get an external hard drive and hook it up via USB for the following reasons:
It improves speed when the database and the app are not located in the same location.
Moving it is soo much easier. Just plug into the new box..., install across, get the instructions from support for the database hookup, and you are done.
When the installation is completed, open across and create the settings as they were in the old database (subject fields, relations, etc.). A little explanation: I work with few clients mostly private on large projects, and therefore not many are there. If you have lots of relations created, it might be better to consider moving the database, but for this make sure to contact the across support team.
Upon completion of the preparatory work, import the CrossTank individual project exports using the settings created in step 3.
Upon completing all importing, reorganize the database.
In the new database, export all TUs into a file and back this one up. Also, keep the old back up labeled and handy for some time, just in case.
Import the CrossTank file previously exported.
In the new termbase, export all entries into a file and back this one up. Also, keep the old back up labeled and handy for some time, just in case.
Translate again and be happy...
A little explanation.
While this particular approach might sound somewhat convoluted, when switching to a new computer, and by just moving the implementation, you will soemtimes see that things from the old get carried onto the new. I am personally not to keen on this because it can cause issues. Id rather start on a clean slate so to speak. Again, this is my prefercne if everything is on one computer. However, my setup is in as far as having and external hard drive for the databases, because it makes life simple.
[Bearbeitet am 2008-09-04 14:51]
| || || |