Unicode Database Upgrade (SQL Financial Accounting 5): Difference between revisions

From eStream Software
 
(172 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==To Do List==
==Check List==
:1. '''[[Backup_Database|Backup]]''' all the databases before upgrade.
:1. '''[[Backup_Database|Backup]]''' all the databases from '''Version 4''' before upgrade.
:2. Remove/Uninstall the previous Firebird version installed, ie. '''1.5''', '''2.0''', '''2.5'''.
:2. '''Remove/Uninstall''' the previous Firebird version installed, ie. '''1.5''', '''2.0''', '''2.5'''.
:3. Install '''Firebird 3.0.1'''.
:3. Install '''[[Firebird_3.0.1_Installation|Firebird 3.0.1]]'''.
:4. SQL Financial Accounting 5 (Version: '''5.2016.790.737''').
:4. Install SQL Financial Accounting 5 (32 bits), version: '''5.2016.790.737'''.
:5. Check the System Locale in Regional setting.
:5. For '''Windows XP''' user ONLY, a minimum requirement must have Service Pack 3 (SP 3). To download the SP3 click [http://download.windowsupdate.com/msdownload/update/software/svpk/2008/04/windowsxp-kb936929-sp3-x86-enu_c81472f7eeea2eca421e116cd4c03e2300ebfde4.exe here].
::5.1 Go to '''Control Panel'''.
'''How to check the Service Pack in Windows XP?'''
::5.2 Look for '''Regional''' setting. See screenshot below.
1. Click on Windows '''Start'''.
2. Right click on '''My Computer'''.
3. Select '''Properties'''.
4. Check and make sure it is '''Service Pack 3'''.
[[File:Core-Unicode_32.jpg]]
<br />
:6. Check the System Locale in Regional setting.
::6.1 Go to '''Control Panel'''.
::6.2 Look for '''Regional''' setting. See screenshot below.
:::[[File:Core-Unicode_14.jpg]]
:::[[File:Core-Unicode_14.jpg]]
<br />
<br />
::5.3 Click on '''Administrative''' tab. Check the Language for non-Unicode programs, eg. English (United States) or Chinese (Simplified, China).
::6.3 Click on '''Administrative''' tab. Check the Language for non-Unicode programs, eg. English (United States) or Chinese (Simplified, China).
:::[[File:Core-Unicode_15.jpg]]
:::[[File:Core-Unicode_15.jpg]]
<br />
<br />
Line 17: Line 25:
   2. What type of language input using? Simplified or Traditional Chinese?  
   2. What type of language input using? Simplified or Traditional Chinese?  
<br />
<br />
:6. Check '''Local C''' drive free spaces (follow the Windows drive). Recommended '''25GB free space or more'''.
:7. Check '''Local C''' drive free spaces (follow the Windows drive). Recommended '''25GB free space or more'''.
:7. '''Restore''' the database from the backup.
:8. '''Restore''' the database from the backup file.
<br />
 
==New Unicode Upgrade Steps (applicable to SQL Accounting version 739 and above)==
Before start upgrade, please make sure all the database must <big>'''BACKUP'''</big>.
:1. '''Uninstall''' the previous Firebird and SQL Financial Accounting version 4.
:2. '''Install''' the SQL Financial Accounting version 5 (version 739 and above).
:3. Execute the SQL Financial Accounting version 5.
:4. At the logon screen, click on a button beside the company name (...).
::[[File:Core-Unicode_41.jpg]]
<br />
:5. Click on '''Back to Database Group'''.
::[[File:Core-Unicode_42.jpg]]
<br />
:6. Right click on the DCF Group and select '''Properties...'''.
::[[File:Core-Unicode_43.jpg]]
<br />
:7. For upgrade database purpose, it is compulsory to change from '''Firebird Server''' to '''Firebird Standalone Database'''. Click OK to exit this screen.
::[[File:Core-Unicode_44.jpg]]
<br />
 
'''Tips: '''
Upgrade database using Firebird Standalone Database setting. You are allow to upgrade the database directly.
:8. Go to login the database to start upgrade.
::[[File:Core-Unicode_45.jpg]]
<br />
<br />


==Unicode Database Upgrade==
:9. Click on '''Yes''' to confirm proceed the database upgrade.
:1. Execute the SQL Financial Accounting 5 (Version: '''5.2016.790.737''').
::[[File:Core-Unicode_46.jpg]]
:2. Restore the database from the backup file.
:3. Login the database restored.
:4. Click on '''Yes''' to confirm proceed the database upgrade.
::[[File:Core-Unicode_01.jpg]]
<br />
<br />
:5. Choose an appropriate encoding. Select '''Default - Windows 1252 ANSI''' if your server current language for non-Unicode programs is "English (United States)".
:10. Choose an appropriate encoding. Select '''Default - Windows 1252 ANSI''' if your server current language for non-Unicode programs is "English (United States)".
::[[File:Core-Unicode_02.jpg]]
::[[File:Core-Unicode_02.jpg]]
<br />
<br />
:6. For more info about choosing a correct encoding, see the check list table below.
:11. For more info about choosing a correct encoding, see the check list table below.
::{| class="wikitable"
::{| class="wikitable"
|-
|-
Line 47: Line 76:
|}
|}
<br />
<br />
:7. Upgrade database started.
:12. Transliterate to Unicode sample list out.
::[[File:Core-Unicode_03.jpg]]
<br />
:8. Transliterate to Unicode sample list out.
::[[File:Core-Unicode_04.jpg]]
::[[File:Core-Unicode_04.jpg]]
<br />
<br />
:9. Click on '''Yes''' to proceed upgrade if you are confirm the characters are meaningful to read.
:13. 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 />


  Note:
  '''Note:'''
  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)
:14. Upgrade database continue... (estimate upgrade duration : 15 -30 mins per database)
::[[File:Core-Unicode_07.jpg]]
::[[File:Core-Unicode_47.jpg]]
<br />
:15. Database upgrade successfully, '''Old Database''' link will be '''DROP''' and '''New Database''' link will be '''ADD''' (new database file created automatically).
::[[File:Core-Unicode_49.jpg]]
<br />
 
'''Example:'''
OLD database filename: ACC-0001.FDB (AUTO DROP)
OLD database filename: ACC-0001-V4.FDB (AUTO RENAME)
NEW database filename: ACC-0002.FDB (AUTO ADD)
<br />
At the new database file (ACC-0002), you will see a remark displayed as '''Unicode from ACC-0001'''.
<br />
 
:16. For '''Standalone''', you can login the database use immediately.
::[[File:Core-Unicode_45.jpg]]
<br />
 
:17. For '''Server Network''', you are required to '''install''' the Firebird 3.0.1. Click [[Firebird_3.0.1_Installation|here]] to get Firebird 3.0.1 installation guide.
 
:18. Go back to DCF Group properties. Change the database engine to '''Firebird Server''' and click on '''Test Connection''' (Server Version: WI-V3.0.1.32609 Firebird 3.0).
::[[File:Core-Unicode_50.jpg]]
<br />
 
==Possible Error and Solution==
===1. Unsupported on-disk structure for file (found 11.2, support 12.0)===
::[[File:Core-Unicode_22.jpg]]
<br />
:<big>'''Solution:'''
:Restore the database from the backup file.</big>
<br />
 
===2. Unable to find vendor library of database with ODS version 11.2===
::[[File:Core-Unicode_23b.jpg]]
<br />
:<big>'''Solution:'''
:Restore the database from the backup file.</big>
<br />
 
 
===3. Access violation at address....in module msxml6.dll===
::[[File:Core-Unicode_23.jpg]]
<br />
:<big>'''Solution:'''
:Retry to upgrade the database again.</big>
<br />
 
===4. The following error(s) have occured invalid class typecast===
::[[File:Core-Unicode_24.jpg]]
<br />
:<big>'''Solution:'''
:Uninstall the previous SQL Account (64 bits). Download the '''setup-x86 file (32 bits)''' and install again.</big>
<br />
 
===5. Cannot transliterate character between character sets===
::[[File:Core-Unicode_25.jpg]]
<br />
:<big>'''Solution:'''
:Run the '''[[Unicode_Database_Upgrade_(SQL_Financial_Accounting_5)#Optional:_Database_Encoding_Diagnosis_.28For_Chinese_only.29|Database Encoding Diagnosis (For Chinese only)]]'''.</big>
<br />
 
===6. Cannot make field X_CODE of table AGENT NOT NULL because there are NULLs present at procedure MIGRATE line:32,col:5===
::[[File:Core-Unicode_33.jpg]]
<br />
:<big>'''Solution:'''
:Make sure you have upgrade the database from '''Version 3 to 4''' first. Next, backup the database from '''Version 4''' and restore into '''Version 5''' to start upgrade.</big>
<br />
 
===7. Malformed String message at Supplier Contra ===
:Edit the Supplier Contra and get prompt this error.
::[[File:Core-Unicode_34.jpg]]
<br />
:<big>'''Solution:'''
:'''Re-download''' the latest SQL Financial Accounting. Uninstall and install the SQL Financial Accounting.</big>
<br />
 
===8. Application Error while try to run the SQL Accounting in Windows XP ===
::[[File:Core-Unicode_35.jpg]]
<br />
:<big>'''Solution:'''
:Update the Windows XP to Service Pack 3. To download the SP3 click [http://download.windowsupdate.com/msdownload/update/software/svpk/2008/04/windowsxp-kb936929-sp3-x86-enu_c81472f7eeea2eca421e116cd4c03e2300ebfde4.exe here].</big>
 
'''How to check the Service Pack in Windows XP?'''
1. Click on Windows '''Start'''.
2. Right click on '''My Computer'''.
3. Select '''Properties'''.
4. Check and make sure it is '''Service Pack 3'''.
[[File:Core-Unicode_32.jpg]]
<br />
<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]]
===9. You are trying to login "" database===
::[[File:Core-Unicode_36.jpg]]
<br />
<br />
:12. Re-login with '''New Database'''. Usually you can identify the new database at the remark, eg. Unicode from Old Database filename.
:<big>'''Solution:'''
::[[File:Core-Unicode_09.jpg]]
:Firstly, '''uninstall''' the SQL Financial Accounting. Check the '''...\SQL Financial Accounting\Bin''' folder. If you have found any filename with extension ie. bpl, dll and exe in that folder, please remove it completely. Lastly, re-install the SQL Financial Accounting again. </big>
<br />
<br />


  Example:
===10. Unable To Locate Component (MSVCR100.dll) database===
  OLD database filename: ACC-0003.FDB (DROP)
::[[File:Core-Unicode_37.jpg]]
  NEW database filename: ACC-0001.FDB (ADD)
<br />
<br />
:<big>'''Solution:'''
At the new database file (ACC-0001), you will see a remark displayed as '''Unicode from ACC-0003'''.
::Follow the below steps.
::'''Steps:'''
::1. Uninstall any existing Microsoft Visual C++ Redistributable Package installed in the PC.
::2. From the list below, download the Microsoft Visual C++ Redistributable Package.
</big>
  For SQL Acc 32 bits: Microsoft Visual C++ 2010 Redistributable Package (x86). Download for Windows 32 bits, click
  [http://www.microsoft.com/download/en/details.aspx?id=5555 HERE].
For SQL Acc 64 bits: Microsoft Visual C++ 2010 Redistributable Package (x64). Download for Windows 64 bits, click
  [http://www.microsoft.com/download/en/details.aspx?id=14632 HERE].
<big>
::3. After download completed, double click to the filename '''vcredist_x86.exe''' to install.
</big>
<br />
 
===11. Prompt access violation on module vcl240.bpl===
: This norm happen on the pc with old version (eg windows xp below service pack 3 or Windows Server 2003 below service pack 2).
 
<big>'''Solution'''
* Just download & install
:- Windows Imaging Component (x86) => https://www.microsoft.com/en-us/download/details.aspx?id=32
:- Windows Imaging Component (x64) => https://www.microsoft.com/en-us/download/details.aspx?id=1385
<br />
</big>
 
===12. Unable to find vendor library for WI-V2.5.6.27020 Firebird 2.5===
: Try to login the database. Get prompt this error.
::[[File:Core-Unicode_51.jpg]]
 
<big>'''Solution'''
: 1. Click on a button beside the company name (...).
::[[File:Core-Unicode_41.jpg]]
: 2. Click on '''Back to Database Group'''.
::[[File:Core-Unicode_42.jpg]]
<br />
: 3. Right click on the DCF Group and select '''Properties...'''.
::[[File:Core-Unicode_43.jpg]]
<br />
<br />
: 4. For upgrade database purpose, it is compulsory to change from '''Firebird Server''' to '''Firebird Standalone Database'''. Click OK to exit this screen.
::[[File:Core-Unicode_44.jpg]]
<br /></big>


==Advantages of Unicode Database==
==Advantages of Unicode Database==
===1. No longer need to set your system locale===
===1. No longer need to set your system locale===
:You able to read, key-in and store the Chinese Simplified characters without change the system locale.  
:You able to read, key-in and store the Chinese Simplified characters without change the system locale.  
::[[File:Core-Unicode_10a.jpg]]
[[File:Core-Unicode_10a.jpg|center|700px]]
<br />
<br />


Line 90: Line 241:
<br />
<br />
:2.2 All reports are support multi-languages.  
:2.2 All reports are support multi-languages.  
::[[File:Core-Unicode_13.jpg]]
[[File:Core-Unicode_13.jpg|center|700px]]
<br />
<br />


Line 99: Line 250:


==Optional: Database Encoding Diagnosis (For Chinese only)==
==Optional: Database Encoding Diagnosis (For Chinese only)==
==='''Reason to use'''===
:Failed to perform database upgrade due to the database could have contains other characters (eg. '''UTF-8''' character set which is copy from others source eg. internet webpage).
<br />
===Steps===
:1. Select encoding option: '''Database Encoding Diagnosis (For Chinese only)'''.
::[[File:Core-Unicode_26.jpg]]
<br />
:2. Select '''Simplified Chinese 简体中文 - GB18030'''.
::[[File:Core-Unicode_27.jpg]]
<br />
:3. For example, if you have found the value is '''not meaningful to read''' in '''Converted Value (By Encoding)''' column, then you have to fix it.
::[[File:Core-Unicode_28.jpg]]
<br />
'''Note:'''
1. If you have found the value is '''meaningful to read''' in '''Converted Value (By Encoding)''' column, then '''do not''' fix it.
2. Click on '''Cancel''' button to exit.
[[File:Core-Unicode_29a.jpg]]
<br />
:4. Click on '''Fix All''' button to fix the value in the list. It will converted as shown in the '''Fix Value (UTF8)''' column.
::[[File:Core-Unicode_29.jpg]]
<br />
'''Note: '''
You can choose to delete the line from the list that you do not wish to fix it. 
<br />
:5. Click on '''No''' to proceed the fixing database encoding.
::[[File:Core-Unicode_30.jpg]]
<br />
:6. Click on '''Yes''' to confirm the fixing database encoding.
::[[File:Core-Unicode_31.jpg]]
<br />
:7. After this, repeat the '''[[Unicode_Database_Upgrade_(SQL_Financial_Accounting_5)#Unicode_Database_Upgrade_Steps|Unicode Database Upgrade Step 3 onwards]]'''.


==See also==
==See also==
* [[Backup Database]]
* [[Backup Database]]
* [[Restore Database]]
* [[Restore Database]]
* [[Firebird 3.0 Installation]]
* [[Firebird 3.0.1 Installation]]

Latest revision as of 03:36, 21 July 2017

Check List

1. Backup all the databases from Version 4 before upgrade.
2. Remove/Uninstall the previous Firebird version installed, ie. 1.5, 2.0, 2.5.
3. Install Firebird 3.0.1.
4. Install SQL Financial Accounting 5 (32 bits), version: 5.2016.790.737.
5. For Windows XP user ONLY, a minimum requirement must have Service Pack 3 (SP 3). To download the SP3 click here.
How to check the Service Pack in Windows XP?
1. Click on Windows Start.
2. Right click on My Computer.
3. Select Properties.
4. Check and make sure it is Service Pack 3.
Core-Unicode 32.jpg


6. Check the System Locale in Regional setting.
6.1 Go to Control Panel.
6.2 Look for Regional setting. See screenshot below.
Core-Unicode 14.jpg


6.3 Click on Administrative tab. Check the Language for non-Unicode programs, eg. English (United States) or Chinese (Simplified, China).
Core-Unicode 15.jpg


Important:
To ensure the encoding conversion correctly, 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? 


7. Check Local C drive free spaces (follow the Windows drive). Recommended 25GB free space or more.
8. Restore the database from the backup file.


New Unicode Upgrade Steps (applicable to SQL Accounting version 739 and above)

Before start upgrade, please make sure all the database must BACKUP.

1. Uninstall the previous Firebird and SQL Financial Accounting version 4.
2. Install the SQL Financial Accounting version 5 (version 739 and above).
3. Execute the SQL Financial Accounting version 5.
4. At the logon screen, click on a button beside the company name (...).
Core-Unicode 41.jpg


5. Click on Back to Database Group.
Core-Unicode 42.jpg


6. Right click on the DCF Group and select Properties....
Core-Unicode 43.jpg


7. For upgrade database purpose, it is compulsory to change from Firebird Server to Firebird Standalone Database. Click OK to exit this screen.
Core-Unicode 44.jpg


Tips: 
Upgrade database using Firebird Standalone Database setting. You are allow to upgrade the database directly.

8. Go to login the database to start upgrade.
Core-Unicode 45.jpg


9. Click on Yes to confirm proceed the database upgrade.
Core-Unicode 46.jpg


10. Choose an appropriate encoding. Select Default - Windows 1252 ANSI if your server current language for non-Unicode programs is "English (United States)".
Core-Unicode 02.jpg


11. 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.


12. Transliterate to Unicode sample list out.
Core-Unicode 04.jpg


13. Click on Yes to proceed upgrade if you are confirm the characters are meaningful to read.
Core-Unicode 05.jpg


Note:
If you have click on No, you will get prompt an operation aborted. Press Ok to exit the message.
Core-Unicode 06.jpg
14. Upgrade database continue... (estimate upgrade duration : 15 -30 mins per database)
Core-Unicode 47.jpg


15. Database upgrade successfully, Old Database link will be DROP and New Database link will be ADD (new database file created automatically).
Core-Unicode 49.jpg


Example:
OLD database filename: ACC-0001.FDB (AUTO DROP)
OLD database filename: ACC-0001-V4.FDB (AUTO RENAME)
NEW database filename: ACC-0002.FDB (AUTO ADD)

At the new database file (ACC-0002), you will see a remark displayed as Unicode from ACC-0001.


16. For Standalone, you can login the database use immediately.
Core-Unicode 45.jpg


17. For Server Network, you are required to install the Firebird 3.0.1. Click here to get Firebird 3.0.1 installation guide.
18. Go back to DCF Group properties. Change the database engine to Firebird Server and click on Test Connection (Server Version: WI-V3.0.1.32609 Firebird 3.0).
Core-Unicode 50.jpg


Possible Error and Solution

1. Unsupported on-disk structure for file (found 11.2, support 12.0)

Core-Unicode 22.jpg


Solution:
Restore the database from the backup file.


2. Unable to find vendor library of database with ODS version 11.2

Core-Unicode 23b.jpg


Solution:
Restore the database from the backup file.



3. Access violation at address....in module msxml6.dll

Core-Unicode 23.jpg


Solution:
Retry to upgrade the database again.


4. The following error(s) have occured invalid class typecast

Core-Unicode 24.jpg


Solution:
Uninstall the previous SQL Account (64 bits). Download the setup-x86 file (32 bits) and install again.


5. Cannot transliterate character between character sets

Core-Unicode 25.jpg


Solution:
Run the Database Encoding Diagnosis (For Chinese only).


6. Cannot make field X_CODE of table AGENT NOT NULL because there are NULLs present at procedure MIGRATE line:32,col:5

Core-Unicode 33.jpg


Solution:
Make sure you have upgrade the database from Version 3 to 4 first. Next, backup the database from Version 4 and restore into Version 5 to start upgrade.


7. Malformed String message at Supplier Contra

Edit the Supplier Contra and get prompt this error.
Core-Unicode 34.jpg


Solution:
Re-download the latest SQL Financial Accounting. Uninstall and install the SQL Financial Accounting.


8. Application Error while try to run the SQL Accounting in Windows XP

Core-Unicode 35.jpg


Solution:
Update the Windows XP to Service Pack 3. To download the SP3 click here.
How to check the Service Pack in Windows XP?
1. Click on Windows Start.
2. Right click on My Computer.
3. Select Properties.
4. Check and make sure it is Service Pack 3.
Core-Unicode 32.jpg


9. You are trying to login "" database

Core-Unicode 36.jpg


Solution:
Firstly, uninstall the SQL Financial Accounting. Check the ...\SQL Financial Accounting\Bin folder. If you have found any filename with extension ie. bpl, dll and exe in that folder, please remove it completely. Lastly, re-install the SQL Financial Accounting again.


10. Unable To Locate Component (MSVCR100.dll) database

Core-Unicode 37.jpg


Solution:
Follow the below steps.
Steps:
1. Uninstall any existing Microsoft Visual C++ Redistributable Package installed in the PC.
2. From the list below, download the Microsoft Visual C++ Redistributable Package.

For SQL Acc 32 bits: Microsoft Visual C++ 2010 Redistributable Package (x86). Download for Windows 32 bits, click 
HERE.
For SQL Acc 64 bits: Microsoft Visual C++ 2010 Redistributable Package (x64). Download for Windows 64 bits, click 
HERE.

3. After download completed, double click to the filename vcredist_x86.exe to install.


11. Prompt access violation on module vcl240.bpl

This norm happen on the pc with old version (eg windows xp below service pack 3 or Windows Server 2003 below service pack 2).

Solution

  • Just download & install
- Windows Imaging Component (x86) => https://www.microsoft.com/en-us/download/details.aspx?id=32
- Windows Imaging Component (x64) => https://www.microsoft.com/en-us/download/details.aspx?id=1385


12. Unable to find vendor library for WI-V2.5.6.27020 Firebird 2.5

Try to login the database. Get prompt this error.
Core-Unicode 51.jpg

Solution

1. Click on a button beside the company name (...).
Core-Unicode 41.jpg
2. Click on Back to Database Group.
Core-Unicode 42.jpg


3. Right click on the DCF Group and select Properties....
Core-Unicode 43.jpg


4. For upgrade database purpose, it is compulsory to change from Firebird Server to Firebird Standalone Database. Click OK to exit this screen.
Core-Unicode 44.jpg


Advantages of Unicode Database

1. No longer need to set your system locale

You able to read, key-in and store the Chinese Simplified characters without change the system locale.
Core-Unicode 10a.jpg


2. Multi-Language Support in Single Database

2.1 Capable to store different language characters (ie. English, Simplified Chinese, Traditional Chinese, Vietnamese, Japanese, Arabic, etc...) in a database.
Core-Unicode 11.jpg


2.2 All reports are support multi-languages.
Core-Unicode 13.jpg


3. Free to search any characters in single database

You are free to search the keyword from the language that has stored in the database.
Core-Unicode 12c.jpg


Optional: Database Encoding Diagnosis (For Chinese only)

Reason to use

Failed to perform database upgrade due to the database could have contains other characters (eg. UTF-8 character set which is copy from others source eg. internet webpage).


Steps

1. Select encoding option: Database Encoding Diagnosis (For Chinese only).
Core-Unicode 26.jpg


2. Select Simplified Chinese 简体中文 - GB18030.
Core-Unicode 27.jpg


3. For example, if you have found the value is not meaningful to read in Converted Value (By Encoding) column, then you have to fix it.
Core-Unicode 28.jpg


Note:
1. If you have found the value is meaningful to read in Converted Value (By Encoding) column, then do not fix it. 
2. Click on Cancel button to exit.
Core-Unicode 29a.jpg


4. Click on Fix All button to fix the value in the list. It will converted as shown in the Fix Value (UTF8) column.
Core-Unicode 29.jpg


Note: 
You can choose to delete the line from the list that you do not wish to fix it.  


5. Click on No to proceed the fixing database encoding.
Core-Unicode 30.jpg


6. Click on Yes to confirm the fixing database encoding.
Core-Unicode 31.jpg


7. After this, repeat the Unicode Database Upgrade Step 3 onwards.

See also