Access violation when applying updates in 4.1 release

[luis_augusto]

When user applies update on a cacheupdated dataset that has no pending updates it is getting an "Access violation.." exception.

Table1.cachedupdate:=true;
Table1.open;
table1.applyupdates; <===="Access violation"
table1.commitupdates;
table1.close;

This had not occurred in previous releases.

[AndreyZ]

Hello,

We already fixed this problem. This fix will be included in the next UniDAC build.

[luis_augusto]

What changes do I have to make in the source code in order do avoid this issue. The last version has corrected an important issue for me and I would not like to step back and wait for the next release.

[AndreyZ]

To avoid this problem, you should replace the following code in the MemData unit (procedure TMemData.ApplyUpdates):

Code: Select all

if OldCurrentItem.Flag = flUsed then
  CurrentItem := OldCurrentItem;

with the following code:

Code: Select all

if (OldCurrentItem = nil) or (OldCurrentItem.Flag = flUsed) then
  CurrentItem := OldCurrentItem;

[WesleyAS]

Hello,

We already fixed this problem. This fix will be included in the next UniDAC build.

Dear AndreyZ, we are modifing our system changing from bde to unidac and we found the same problem. Occours that we dont have the source code to make changes. Please, do you have a prevision of a new build?

Best Regards.
Gelson / Wesley

[AndreyZ]

We are going to release the new UniDAC build in a week or two.

[Uli65]

We are going to release the new UniDAC build in a week or two.

When will the new build released?

[AlexP]

Hello,

The new build will be released next week.