Why still exists the serious bug in UniDAC 2.0 under D12

Discussion of open issues, suggestions and bugs regarding UniDAC (Universal Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
coolzew
Posts: 10
Joined: Sun 17 Apr 2005 04:04

Why still exists the serious bug in UniDAC 2.0 under D12

Post by coolzew » Sun 14 Dec 2008 02:13

Hello,
Today I retest the bug I issued under UniDAC2.0.
http://devart.com/forums/viewtopic.php?t=13464

Other problem stlll exists, how disappointment I am.

The steps is like:http://devart.com/forums/viewtopic.php?t=13464

TuniQuery do not set "insert sql","Update sql"......
A Field origin value is "华源", Field Type is varchar.
1. Edit the Field, set value to "华源中國", Post it, it is ok no problem.
2. Edit the origin value "华源中國" to "华源中", post it , it is no problem.
3. Edit the origin value "华源中" to "华源", post it , It will occurs error as blew.
---------------------------
Project1
---------------------------
Update failed. Found 0 records.
---------------------------
确定
---------------------------

So I canot use the vcl in delphi2009, Pls fix it ASAP.

Dimon
Devart Team
Posts: 2910
Joined: Mon 05 Mar 2007 16:32

Post by Dimon » Tue 16 Dec 2008 11:28

Thank you for information. We have reproduced this problem and fixed it. This fix will be included in the next UniDAC build.

coolzew
Posts: 10
Joined: Sun 17 Apr 2005 04:04

Post by coolzew » Sun 11 Jan 2009 04:58

Error:
if (ParamVarType = varOleStr) {$IFDEF VER12P} or (ParamVarType = varUString) or (ParamVarType = varString){$ENDIF} then // WideString
l := Integer(StrLenW(ParamVarPtr) * SizeOf(WideChar))
else // Pascal string
l := Length(ParamDesc.Value);

Correct:
if (ParamVarType = varOleStr) {$IFDEF VER12P} or (ParamVarType = varUString) {$ENDIF} then // WideString
l := Integer(StrLenW(ParamVarPtr) * SizeOf(WideChar))
else // Pascal string
{$IFDEF VER12P}
l := Length(AnsiString(ParamDesc.Value));
{$ELSE}
l := Length(ParamDesc.Value);
{$ENDIF}[/code]

Dimon
Devart Team
Posts: 2910
Joined: Mon 05 Mar 2007 16:32

Post by Dimon » Tue 13 Jan 2009 09:58

Thank you for the advice. We will fix this code in the next UniDAC build.

Post Reply