🚀 go-pugleaf

I will use the Provider BeforeUpdateRecord to handle this. thanks

--

-----------------------------------------------------------------
PIQUOT J�r�me
A. WOLFF SA
6, rue de la Gare
67120 ERNOLSHEIM/BRUCHE
FRANCE
e-mail: wolff@media-net.fr
http://www.media-net.fr/wolff
-----------------------------------------------------------------
Matt Jacobs <mattja@ix.netcom.com> a �crit dans le message :
7pd65r$jr8@forums.borland.com...
> If concurrency is not an issue for you. For instance, if you know no
> one but yourself will be editing the records you are editing, then
> what you can do is change the UpdateMode from UpWhereAll to
> UpWhereKeyOnly. As long as your primary key is not a floating point or
> datetime field (hidden floating point), then you will be okay.
> UpWhereChanged in not usually a lot of help. It has the potential to
> decrease the odds you will have the edit error, but it does not solve
> the problem. UpWhereChanged can decrease the complexity of the WHERE
> clause in the SQL statement that is generated, but in order to know
> what changed, the BDE still must perform an internal comparison. If
> this comparison contains floating point values, then the possibility
> exists the rouding error will take place there, inside the bowels of
> the BDE (which is the most likely place for the error).
>
> On the other hand, if you and someone else perform concurrent edits on
> these same records, you need another solution. UpWhereKeyOnly will not
> help you because you need UpWhereChanged so you will be notified the
> record was actually changed by someone else while you were editing it
> yourself.
>
> Matt Jacobs
>
>
>
> --
>
> My reply-to address is purposely mangled to thwart auto-reply bots.
> Please remove the two leading underscores if you wish to reply via
> e-mail.
>