Unicode Database Upgrade (SQL Financial Accounting 5): Difference between revisions
From eStream Software
No edit summary |
|||
| Line 52: | Line 52: | ||
::[[File:Core-Unicode_04.jpg]] | ::[[File:Core-Unicode_04.jpg]] | ||
<br /> | <br /> | ||
:9. Click on '''Yes''' to proceed if you are confirm the characters are meaningful to read. | :9. Click on '''Yes''' to proceed upgrade if you are confirm the characters are meaningful to read. | ||
::[[File:Core-Unicode_05.jpg]] | ::[[File:Core-Unicode_05.jpg]] | ||
<br /> | <br /> | ||
| Line 59: | Line 59: | ||
If you have click on '''No''', you will get prompt an '''operation aborted'''. Press '''Ok''' to exit the message. | If you have click on '''No''', you will get prompt an '''operation aborted'''. Press '''Ok''' to exit the message. | ||
[[File:Core-Unicode_06.jpg]] | [[File:Core-Unicode_06.jpg]] | ||
:10. Upgrade database continue... (estimate upgrade duration : 15 -30 mins per database) | |||
::[[File:Core-Unicode_07.jpg]] | |||
<br /> | |||
:11. Database upgrade successfully, '''Old Database''' link will be '''DROP''' and '''New Database''' link will be '''ADD''' (new database file created automatically). | |||
::[[File:Core-Unicode_08.jpg]] | |||
<br /> | |||
:12. Re-login with '''New Database'''.Usually you can identify new database at the remark, eg. Unicode from Old Database filename. | |||
::[[File:Core-Unicode_09.jpg]] | |||
<br /> | |||
<br /> | |||
==Unicode Database Features== | ==Unicode Database Features== | ||
Revision as of 04:14, 5 November 2016
To Do List
- 1. Backup all the databases.
- 2. Remove/Uninstall the previous Firebird version installed, ie. 1.5, 2.0, 2.5.
- 3. Install Firebird 3.0.
- 4. SQL Financial Accounting 5 (Version: 5.2016.790.737).
- 5. Check the System Locale in Regional setting.
- 5.1 Go to Control Panel.
- 5.2 Look for Regional setting. See screenshot below.
- 5.3 Click on Administrative tab. Check the Language for non-Unicode programs, eg. English (United States) or Chinese (Simplified, China).
- 5.3 Click on Administrative tab. Check the Language for non-Unicode programs, eg. English (United States) or Chinese (Simplified, China).
Note: Please ask the user the following questions: 1.Do you key-in any Chinese or other than English words in the database?. 2. What type of language input using? Simplified or Traditional Chinese?
- 6. Check Local C drive free spaces (follow the Windows drive). Recommended 25GB free space or more.
Unicode Database Upgrade
- 1. Execute the SQL Financial Accounting 5 (Version: 5.2016.790.737).
- 2. Restore the database from the backup file.
- 3. Login the database restored.
- 4. Click on Yes to confirm proceed the database upgrade.
- 5. Choose an appropriate encoding. Select Default - Windows 1252 ANSI if your server current language for non-Unicode programs is "English (United States)".
- 6. For more info about choosing a correct encoding, see the check list table below.
No. SQL encoding Regional setting (non-Unicode language) 1. Defaul-Windows 1252 ANSI All English, ie. English (United Kingdom), English (Malaysia), English (Singapore), etc. 2. Simplified Chinese 简体中文 Chinese Simplified ONLY, ie. Chinese (Simplified, China), Chinese (Simplified, Singapore) 3. Traditional Chinese 繁体中文 Chinese Traditional ONLY, ie. Chinese (Traditional, Hong Kong SAR), Chinese (Traditional, Taiwan) 4. Firebird NONE character set NONE encoding (Not recommended to use). For Firebird programmer use. 5. Database Encoding Diagnosis (For Chinese only To analyse the encoding (for Chinese character) able to read by your eyes.
- 7. Upgrade database started.
- 8. Transliterate to Unicode sample list out.
- 9. Click on Yes to proceed upgrade if you are confirm the characters are meaningful to read.
Note:
If you have click on No, you will get prompt an operation aborted. Press Ok to exit the message.
- 10. Upgrade database continue... (estimate upgrade duration : 15 -30 mins per database)
- 11. Database upgrade successfully, Old Database link will be DROP and New Database link will be ADD (new database file created automatically).
- 12. Re-login with New Database.Usually you can identify new database at the remark, eg. Unicode from Old Database filename.
