Roy,
> I downloaded your app and had a play and came up with two solutions:
>
> 1. Wrap a transaction around the activity
> 2. Set Session.StrictChangeDetection to true
>
> I only ran one test with each but both seem to cure the problem.
>
I have tried 2. with a more complex test program and the problem didn't
happen.
Thanks a lot for the hint.

Bernd Kuhlmann

Tim,
>
> << our customers have reported that changes to a record are not always
> saved but that they seem to be canceled. I have posted a sample project to
> the binaries group. >>
>
> It's a bug.  Basically the BLOB change detection is refreshing the record
> during modification.  A fix will be available shortly.
>
I have seen that the web page with the incident reports for version 4.22 has
been updated on Sunday, March 12, 2006 at 06:39 PM but this bug isn't
mentioned and the download page still refers to build 6.
Can you say when the new build will be available?

Bernd Kuhlmann

Tim,
>> It's a bug.  Basically the BLOB change detection is refreshing the record
>> during modification.  A fix will be available shortly.
>>
>I have seen that the web page with the incident reports for version 4.22 has
>been updated on Sunday, March 12, 2006 at 06:39 PM but this bug isn't
>mentioned and the download page still refers to build 6.
>Can you say when the new build will be available?

I just received your email. There was a misunderstanding: i thought that you would roll out a new build.
I will use the dbisamen.pas you send me so you can ignore my previous posting.

Bernd Kuhlmann

Hello Tim,

in one of our applications we make extensive use of storing various parts of
a journal in a number of blob fields in an encrypted table version 3.30. We
are  moving the application to 4.22 build 6. Would you think this bug  could
have an effect on the contents of two different blob fields both being
edited before the final posting of the record  ? (Edit 2 cancelling edit1).
If so we would appreciate a fix if possible when not having the source
version of Dbisam.

Nils T. Sørensen


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> skrev i melding
news:1CAE407B-61E3-42EF-BD56-7BC1C1659479@news.elevatesoft.com...
> Bernd,
>
> << our customers have reported that changes to a record are not always
> saved but that they seem to be canceled. I have posted a sample project to
> the binaries group. >>
>
> It's a bug.  Basically the BLOB change detection is refreshing the record
> during modification.  A fix will be available shortly.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Nils,

<< in one of our applications we make extensive use of storing various parts
of a journal in a number of blob fields in an encrypted table version 3.30.
We are  moving the application to 4.22 build 6. Would you think this bug
could have an effect on the contents of two different blob fields both being
edited before the final posting of the record  ? (Edit 2 cancelling
edit1).If so we would appreciate a fix if possible when not having the
source version of Dbisam. >>

A new build will be available Monday that fixes this issue.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

any news about the announced new build ?

Nils

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> skrev i melding
news:AD4ADC84-ECB7-4B2F-902C-9832B556328D@news.elevatesoft.com...
> Nils,
>
> << in one of our applications we make extensive use of storing various
> parts of a journal in a number of blob fields in an encrypted table
> version 3.30. We are  moving the application to 4.22 build 6. Would you
> think this bug could have an effect on the contents of two different blob
> fields both being edited before the final posting of the record  ? (Edit 2
> cancelling edit1).If so we would appreciate a fix if possible when not
> having the source version of Dbisam. >>
>
> A new build will be available Monday that fixes this issue.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>
>

Nils,

<< any news about the announced new build ? >>

My apologies for the delays.  I will be wrapping it up this afternoon, so it
should not be any later than tomorrow morning.

--
Tim Young
Elevate Software
www.elevatesoft.com