Another bug with UseUnicode!

upscene · Post by **upscene** » 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

Roaster2 · Post by **Roaster2** » Thu 11 Feb 2010 11:58

I guess Martijn you will deserve a free extension, I'm pretty sure you will.

I'm following the threads here quite a long time yet and noticed that most of the bug reports are from yourself the last weeks.

I hope I do not have a time-limited license to get an almost bug-free version after you have finished your Unicode conversion

Challenger · Post by **Challenger** » Fri 12 Feb 2010 14:42

Martijn, thank you for your work. We appreciate it. I have tried on Firebird 2.5, Delphi 2009 and IBDAC 3.10.0.11 but did not reproduce the error. Please compose a small sample and send it to us. Or contact us by email and we will send our sample.

upscene · Post by **upscene** » Fri 12 Feb 2010 21:02

Sorry, it was InterBase EMPLOYEE db I tried this on... IB 2009.

Fails for me every time.

Dimon · Post by **Dimon** » Tue 16 Feb 2010 09:22

The investigation of the problem is in progress. As soon as we solve the problem we will let you know.

Dimon · Post by **Dimon** » Wed 24 Feb 2010 14:21

We have reproduced this problem and fixed it. This fix will be included in the next IBDAC build.

upscene · Post by **upscene** » Thu 25 Feb 2010 11:31

Dimon wrote:We have reproduced this problem and fixed it. This fix will be included in the next IBDAC build.

Excellent...

I'm waiting for 5 issues now

Any idea when this new release is available?

Dimon · Post by **Dimon** » Thu 25 Feb 2010 13:54

The next IBDAC build will be released in the course of the next week.