|
Deleted
deleted
4116 Posts |
 Posted - 03 July 2002 : 15:56:10
|
The database structure of v4b03.x is the same as v3.3.03. It even shows it as v3.3.03, so do not try to upgrade. Although I call v4b03.004 to be equivalent to v3.3.05, I only did include the security related fixes between v3.3.03 and v3.3.05 and left the other changes as is. Thus, the database related (small) changes (actually fixes) in v3.3.05 are not included in v4b03.004.
With v3.4 there will be some database changes, and I will add more (internationalization related) database changes into v4b04, which will be based on v3.4...
In short, you can use your database with v4b03.x...
BUT, one problem can arise with the international characters. The best solution to provide multilingual data through a database is to use a unicode compatible database. MS Access 2000, MS Access 2002, MS SQL Server 2000 support it fully. MS SQL Server 7 has single language support, MS SQL Server 6.5 does not have any support (I think, but I'm not sure). I don't have any idea on MySQL yet.
MS Access 97 does not support unicode, so you have to upgrade it to Access 200x. In some installations, this corrupts the international characters. For example, this is the case in Turkish. It works OK in local installation, but whenever I move it to the remote host on USA (which definetely has a different locale) some characters got replaced with other chars. I couldn't find a soluton for this.
So, try and see if it works for you.
Think Pink
==> Start Internationalization Here< |
 |
|
Forum Locked
