Another bug with UseUnicode!
Posted: Thu 11 Feb 2010 11:02
Hi,
Try this:
TIBCConnection to EMPLOYEE sample database
TIBCQuery, DescribeParams = True, " select * from employee "
TDataSource linked to the query
TDBGrid, linked to TDataSource
Open the query, run the application. Change a "DEPT_NO" value and move away from the record (change it to, for example, "621", a valid value).
This works fine.
Now, set UseUnicode to True.
Open the query, run the application, change the value again. You'll get:
violation of FOREIGN KEY constraint "INTEG_28" on table "EMPLOYEE"
Changing another value, eg "PHONE_EXT" results in only the first character being saved to the database.
Yet another UseUnicode bug...
How many more bugs do I have to discover in order to get a free extension of upgrades? Up till now, the component set is hardly usable.
With regards,
Martijn Tonies
Upscene Productions
Try this:
TIBCConnection to EMPLOYEE sample database
TIBCQuery, DescribeParams = True, " select * from employee "
TDataSource linked to the query
TDBGrid, linked to TDataSource
Open the query, run the application. Change a "DEPT_NO" value and move away from the record (change it to, for example, "621", a valid value).
This works fine.
Now, set UseUnicode to True.
Open the query, run the application, change the value again. You'll get:
violation of FOREIGN KEY constraint "INTEG_28" on table "EMPLOYEE"
Changing another value, eg "PHONE_EXT" results in only the first character being saved to the database.
Yet another UseUnicode bug...
How many more bugs do I have to discover in order to get a free extension of upgrades? Up till now, the component set is hardly usable.
With regards,
Martijn Tonies
Upscene Productions