Thomas,

 This from an SDL Architect...

I can confirm I also have problems with the provided  termbases, but not why so far. I don't know the code used to create the data, the function mentioned in the report is none of ours.  I tried creating a termbase and importing the provided data myself and it looks OK. Maybe a look at the code I used is helpful.

// Create and open local termbase repository

Sdl.MultiTerm.TMO.Interop.Application _Mt = new Sdl.MultiTerm.TMO.Interop.Application();

TermbaseRepository tr = _Mt.LocalRepository;

tr.Connect("", "");

// Create new file based termbase

Termbase tb = _Mt.LocalRepository.Termbases.New("tempTermbase", "programmatically created",

   @"D:\Data\2009Definition for Test_JA.xdt",

   @"D:\Data\New Termbase.sdltb");

// inject file paths into import definition (alternatively create an import definition in the wizard

// with the files filled in)

string tmpPath = System.Environment.GetEnvironmentVariable("TEMP") + "\\tmpImportDefinition.xml";

_Tb.ImportDefinitions["Default import definition"].Save(tmpPath);

XmlDocument doc = new XmlDocument();

doc.Load(tmpPath);

XmlNode node = doc.SelectSingleNode("//XMLFile");

node.InnerXml = @"D:\Data\testexportxml1.xml";

node = doc.SelectSingleNode("//ErrorFile");

node.InnerXml = @"D:\Data\testexportxml1.xml.import.log";

doc.Save(tmpPath);

// use modified definition for import

ImportDefinition modified = _Tb.ImportDefinitions.Add("tmpImport", "", tmpPath);

modified.ProcessImport(MtTaskType.mtScript);

// clean up

modified.Delete();

System.IO.File.Delete(tmpPath);

tr.Disconnect();

Thomas,

 This from an SDL Architect...

I can confirm I also have problems with the provided  termbases, but not why so far. I don't know the code used to create the data, the function mentioned in the report is none of ours.  I tried creating a termbase and importing the provided data myself and it looks OK. Maybe a look at the code I used is helpful.

// Create and open local termbase repository

Sdl.MultiTerm.TMO.Interop.Application _Mt = new Sdl.MultiTerm.TMO.Interop.Application();

TermbaseRepository tr = _Mt.LocalRepository;

tr.Connect("", "");

// Create new file based termbase

Termbase tb = _Mt.LocalRepository.Termbases.New("tempTermbase", "programmatically created",

   @"D:\Data\2009Definition for Test_JA.xdt",

   @"D:\Data\New Termbase.sdltb");

// inject file paths into import definition (alternatively create an import definition in the wizard

// with the files filled in)

string tmpPath = System.Environment.GetEnvironmentVariable("TEMP") + "\\tmpImportDefinition.xml";

_Tb.ImportDefinitions["Default import definition"].Save(tmpPath);

XmlDocument doc = new XmlDocument();

doc.Load(tmpPath);

XmlNode node = doc.SelectSingleNode("//XMLFile");

node.InnerXml = @"D:\Data\testexportxml1.xml";

node = doc.SelectSingleNode("//ErrorFile");

node.InnerXml = @"D:\Data\testexportxml1.xml.import.log";

doc.Save(tmpPath);

// use modified definition for import

ImportDefinition modified = _Tb.ImportDefinitions.Add("tmpImport", "", tmpPath);

modified.ProcessImport(MtTaskType.mtScript);

// clean up

modified.Delete();

System.IO.File.Delete(tmpPath);

tr.Disconnect();

Update from an SDL Architect...

It looks like the termbase was created correctly, but the import: tbNew.newEntry(content,  false).  seems to have been passed the content of "testexportxml1.xml" as a parameter. This file is an export of the complete termbase, but Entries.New (the function probably used inside newEntry) takes the xml for a single entry. The format is briefly described in the sdk help, or you can export a single entry from the desktop client as a template:note that in that case you need to remove the <concept> group.