Subject | DELPHI2009 and Firebird |
---|---|
Author | ICAMSoft:Info |
Post date | 2008-11-02T20:26:11Z |
Trying to test D2009 and Firebird i had the following problem:
When the FB database has UTF8 fields:
Case 1: using the IBXpress Components provided by D2009 i get a message
Division by zero when trying to connect
Case 2: using DBExress Components provided by D2009 the Delphi IDE freeze
Case 3: using last ODBC firebierd driver and DbGo (ADO) provided by D2009
the same as case 2
In all of the above cases if in the select sql (that causes the connection),
i don't mention any UTF8 field, the error doesn't happen
Other Points
In other databases of mine not having UTF8 fields, the connection functions
properly with all fields.
The databases - these with UTF8 fields - that have problem, function
properly with D7
Enviroment
Delphi 2009
FB SServer / FbClient.dll / GDS32.DLL build 17910 Databases are created by
FB 2.1.1 version
Windows XP SP3
(all on a fresh VMWare installation that has been done only for testing)
Is this a known problem? If yes, any workaround?
Thanks in advance for any reply
A.Kyriakos
Best Regards
Athens, Greece
[Non-text portions of this message have been removed]
When the FB database has UTF8 fields:
Case 1: using the IBXpress Components provided by D2009 i get a message
Division by zero when trying to connect
Case 2: using DBExress Components provided by D2009 the Delphi IDE freeze
Case 3: using last ODBC firebierd driver and DbGo (ADO) provided by D2009
the same as case 2
In all of the above cases if in the select sql (that causes the connection),
i don't mention any UTF8 field, the error doesn't happen
Other Points
In other databases of mine not having UTF8 fields, the connection functions
properly with all fields.
The databases - these with UTF8 fields - that have problem, function
properly with D7
Enviroment
Delphi 2009
FB SServer / FbClient.dll / GDS32.DLL build 17910 Databases are created by
FB 2.1.1 version
Windows XP SP3
(all on a fresh VMWare installation that has been done only for testing)
Is this a known problem? If yes, any workaround?
Thanks in advance for any reply
A.Kyriakos
Best Regards
Athens, Greece
[Non-text portions of this message have been removed]