Unicode Database Upgrade (SQL Financial Accounting 5)

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.

6. Check the System Locale in Regional setting.

6.1 Go to Control Panel.

6.2 Look for Regional setting. See screenshot below.

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

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 (...) button.

5. Click on Back to Database Group.

6. Right click on the DCF Group and select Properties....

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

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

8. Go to login the database.

9. Click on Yes to confirm proceed the database upgrade.

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

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.

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

14. Upgrade database continue... (estimate upgrade duration : 15 -30 mins per database)

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

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 users, you can login the database and use it.

17. For Network users only, 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).

Possible Error and Solution

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

Solution:

Restore the database from the backup file.

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

Solution:

Restore the database from the backup file.

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

Solution:

Retry to upgrade the database again.

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

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

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

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.

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

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.

9. You are trying to login "" database

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

Solution:

You may uninstall any existing Microsoft Visual C++ Redistributable Package and install the latest Microsoft Visual C++ 2010 Redistributable Package and check if it helps.

Step 1:

Uninstall the package:

a. Open Programs and Features.

b. From the list, find Microsoft Visual C++ Redistributable Package and click on it.

c. Click Uninstall at the top of the list.

Step 2:

Microsoft Visual C++ 2010 Redistributable Package (x86). Download for Windows 32 bits, click HERE.

Microsoft Visual C++ 2010 Redistributable Package (x64). Download for Windows 64 bits, click HERE.

11. Prompt access violation on module vcl240.bpl

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

Solution

Just download & install

Windows Imaging Component => https://www.microsoft.com/en-us/download/details.aspx?id=32

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.

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.

2.2 All reports are support multi-languages.

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.

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

2. Select Simplified Chinese 简体中文 - GB18030.

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.

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.

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

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.

6. Click on Yes to confirm the fixing database encoding.

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

See also

• Backup Database
• Restore Database
• Firebird 3.0.1 Installation