Support forum of the software localization tool Sisulizer


Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 

 Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
Problem with a SQLServer Database localization - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ...
AuthorPost
 Posted: Wed Dec 19th, 2007 10:29 am
PM Quote Reply
cprior
Member
 

Joined: Wed Dec 12th, 2007
Location:  
Posts: 3
Status: 
Offline
Hello,

I`m trying to localize a SQL Database, with some tables defined as follow (you can see some of them in the image attached):
   
    - Type (int)             --> Primary Key
    - LanguajeID (int)    --> Primary key
    - Name (nvarchar)

When I open the Sisulizer Wizard and scan the database, it shows all my tables, but not the columns (Type and LanguajeId are missing), so I can't set these fields as Languaje ID Field and Next button is never available.

What I'm doing wrong?

Thank you

Attachment: image.gif (Downloaded 10 times)

Back To Top PM Quote Reply

 Posted: Thu Dec 20th, 2007 08:35 am
PM Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Tokyo, Japan
Posts: 1641
Status: 
Offline
It seems just ok. For some reason Sisulizer does not see LanguageId field as potential language id field.

What is the type of udtCOUNT(int) type?

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Quote Reply

 Posted: Thu Dec 20th, 2007 11:19 am
PM Quote Reply
cprior
Member
 

Joined: Wed Dec 12th, 2007
Location:  
Posts: 3
Status: 
Offline
It's this user-defined type:

Attachment: image1.gif (Downloaded 8 times)

Back To Top PM Quote Reply

 Posted: Thu Dec 20th, 2007 11:23 am
PM Quote Reply
cprior
Member
 

Joined: Wed Dec 12th, 2007
Location:  
Posts: 3
Status: 
Offline
udtENUM is the same as udtCOUNT.

I don't know why there are two different user-defined types to do the same...

Back To Top PM Quote Reply

 Posted: Thu Dec 20th, 2007 12:14 pm
PM Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Tokyo, Japan
Posts: 1641
Status: 
Offline
The problem is the LanguageID field. Current it is int and it has to be string (e.g. NVARCHAR). Sisulizer uses ISO language codes in the language field and those codes are strings. For example

English = en
English (US) = en-US

German = de
German (Switzerland) = de-CH

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Quote Reply

Current time is 12:55 am  
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Problem with a SQLServer Database localization



WowUltra 1.11 Copyright © 2007 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize