New Unidac 4.1.4 has serious bugs in table commit

Discussion of open issues, suggestions and bugs regarding UniDAC (Universal Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
pimentel_flores
Posts: 31
Joined: Wed 15 Aug 2007 16:30
Location: mexico

New Unidac 4.1.4 has serious bugs in table commit

Post by pimentel_flores » Mon 13 Feb 2012 19:41

Hi Unidac Team,

I just downloaded and installed the new 4.1.4 version of the unidac
and now my project is showing this kind of errors

Access violation at address 0062BAAB in module 'Project.exe'. Read of address 00000016

and

AddRefStr failed
(D:\Projects\Delphi\Dac\Common\Source\MemData.pas, line 7952)

and also this piece of code is not working anymore, it throws erros and cannot save information to my tables

Code: Select all

 
               uniquery.ApplyUpdates;
               uniquery.CommitUpdates;
               uniquery.RefreshRecord;

im using delphi 2007, unidac 4.1.4 with connection to mysql 5.1

AndreyZ

Post by AndreyZ » Tue 14 Feb 2012 07:04

Hello,

We already fixed the problem with Access Violation on ApplyUpdates. Please describe the situation (the code) when the "AddRefStr failed" assertion failure occurs in more details. Also, please note that you don't need to call ApplyUpdates before CommitUpdates. If there are pending updates in a dataset, the CommitUpdates method calls ApplyUpdates.

pimentel_flores
Posts: 31
Joined: Wed 15 Aug 2007 16:30
Location: mexico

Hi Devart Team

Post by pimentel_flores » Fri 16 Mar 2012 22:28

Sorry for being late on replying,
I was assigned to other project but now will get back on this issue.

so far i think the issue is the refreshrecord call, i think this cannot be called after the commit.

will try removing this and will let you know

Code: Select all

               
uniquery.ApplyUpdates; 
uniquery.CommitUpdates; 
[b]uniquery.RefreshRecord;[/b]

AndreyZ

Post by AndreyZ » Mon 19 Mar 2012 08:37

I cannot reproduce the problem with the "AddRefStr failed" assertion failure in the way you pointed out above. Please try creating a small sample to demonstrate the problem and send it to andreyz*devart*com .

pimentel_flores
Posts: 31
Joined: Wed 15 Aug 2007 16:30
Location: mexico

Not able to replicate

Post by pimentel_flores » Thu 29 Mar 2012 22:03

Hi, I upgrade my unidac version to the lastest, now the error message doesnt appear anymore,

i will put this new version in production and see how does this behave in full service. will let you know

AndreyZ

Post by AndreyZ » Fri 30 Mar 2012 11:54

It is good to see that this problem was solved. Feel free to contact us if you have any further questions about UniDAC.

Post Reply