Hi,
I've a program that previously use dbisam 4.17 to do cacheupdate in master
details linked table. But after update to 4.22 it become unstable due to the
locking error. I think that might be some problem with cachesupdate that you
have changed in this latest update.

Isaacs,

<< I've a program that previously use dbisam 4.17 to do cacheupdate in
master details linked table. But after update to 4.22 it become unstable due
to the locking error. I think that might be some problem with cachesupdate
that you have changed in this latest update. >>

Could you be more specific ?  What error are you getting and what code are
you using to generate the error ?

--
Tim Young
Elevate Software
www.elevatesoft.com

I thinks that is autoinc problem. When I assigned autoinc as primary field
in a table and use master-details and cacheupdate the table during the
multiple session, the record will update if least than 5 affected but if
more than 5 the record locking error due to pointer will occur.

Another issue is when during the cache update the last autoinc will not
increase and may cause the duplicate primary key if I using two pc to update
one table.

Hope it's clear. Thanks.


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:54900D6A-0DEE-4D2C-90B2-53E3AA1B0879@news.elevatesoft.com...
> Isaacs,
>
> << I've a program that previously use dbisam 4.17 to do cacheupdate in
> master details linked table. But after update to 4.22 it become unstable
> due to the locking error. I think that might be some problem with
> cachesupdate that you have changed in this latest update. >>
>
> Could you be more specific ?  What error are you getting and what code are
> you using to generate the error ?
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Isaacs,

<< I thinks that is autoinc problem. When I assigned autoinc as primary
field in a table and use master-details and cacheupdate the table during the
multiple session, the record will update if least than 5 affected but if
more than 5 the record locking error due to pointer will occur. >>

I'm still a little unsure of what you're saying.  What is the significance
of the 5 record updates ?  Does the 6th update to a record cause a record
lock error ?  What is the exact error message that you're receiving ?

<< Another issue is when during the cache update the last autoinc will not
increase and may cause the duplicate primary key if I using two pc to update
one table. >>

You'll need to use the OnCachedUpdateError event handler to handle conflicts
like that.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

I've changed the autoinc index field to int field type but problem still
exist. The error code is DBISAM 8708 Record has been changed or deleted by
another user, session, or table cursor in the table 'acknowledge_item'.

This table is linked to master table as master-details relation and this
error is happens when I trying to random change/edit/delete items in the
details table by using transaction with applychange / cancelcachedupdates.

~Isaacs

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:73B85038-B9F2-4895-A18A-459D6E947048@news.elevatesoft.com...
> Isaacs,
>
> << I thinks that is autoinc problem. When I assigned autoinc as primary
> field in a table and use master-details and cacheupdate the table during
> the multiple session, the record will update if least than 5 affected but
> if more than 5 the record locking error due to pointer will occur. >>
>
> I'm still a little unsure of what you're saying.  What is the significance
> of the 5 record updates ?  Does the 6th update to a record cause a record
> lock error ?  What is the exact error message that you're receiving ?
>
> << Another issue is when during the cache update the last autoinc will not
> increase and may cause the duplicate primary key if I using two pc to
> update one table. >>
>
> You'll need to use the OnCachedUpdateError event handler to handle
> conflicts like that.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Isaacs,

<< I've changed the autoinc index field to int field type but problem still
exist. The error code is DBISAM 8708 Record has been changed or deleted by
another user, session, or table cursor in the table 'acknowledge_item'.

This table is linked to master table as master-details relation and this
error is happens when I trying to random change/edit/delete items in the
details table by using transaction with applychange / cancelcachedupdates.
>>

I'm going to need an example project before I can proceed any further.  I
really can't do anything else for you with such a general description.

--
Tim Young
Elevate Software
www.elevatesoft.com

After I carefully tested, I found that it happens when I changed the last
record of detail table and applycacheupdate. The locking error message will
appear in this new version but not in older version.

How do I solve this locking issue by using onCahdUpdateError?


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:05CF90D8-BDF0-40ED-80F8-6294F3BAC5F8@news.elevatesoft.com...
> Isaacs,
>
> << I've changed the autoinc index field to int field type but problem
> still exist. The error code is DBISAM 8708 Record has been changed or
> deleted by another user, session, or table cursor in the table
> 'acknowledge_item'.
>
> This table is linked to master table as master-details relation and this
> error is happens when I trying to random change/edit/delete items in the
> details table by using transaction with applychange / cancelcachedupdates.
> >>
>
> I'm going to need an example project before I can proceed any further.  I
> really can't do anything else for you with such a general description.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Isaacs,

<< After I carefully tested, I found that it happens when I changed the last
record of detail table and applycacheupdate. The locking error message will
appear in this new version but not in older version.

How do I solve this locking issue by using onCahdUpdateError? >>

Could you please send me an example of what you're describing ?  That way I
can test it here and give you further information on what exactly is going
on.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

Thanks for your feedback. I've done a very simple example to illustrate the
problem that I've encountered.

Please extract this rar and compile it with delphi 2005. Click "Test
Problem" button to see the problem. Thanks.

Regards,
Isaacs



"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:906965A6-4191-4907-9FBF-C1FFADD8DA67@news.elevatesoft.com...
> Isaacs,
>
> << After I carefully tested, I found that it happens when I changed the
> last
> record of detail table and applycacheupdate. The locking error message
> will
> appear in this new version but not in older version.
>
> How do I solve this locking issue by using onCahdUpdateError? >>
>
> Could you please send me an example of what you're describing ?  That way
> I
> can test it here and give you further information on what exactly is going
> on.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Isaacs,

<< Thanks for your feedback. I've done a very simple example to illustrate
the problem that I've encountered.

Please extract this rar and compile it with delphi 2005. Click "Test
Problem" button to see the problem. Thanks. >>

Thanks.  I will let you know what I find out.

--
Tim Young
Elevate Software
www.elevatesoft.com