Excellent observation and explanation.
There are indeed some controls and editing styles that make AutoEdit
problematic.

Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

-- We may not have it all together --
-- But together we have it all --

----- Original Message -----
From: "Marco Menardi" <mmenaz@...>
To: <IBObjects@yahoogroups.com>
Sent: Friday, November 29, 2002 6:57 AM
Subject: [IBO] Re: cache sync - before edit


> Just some thoughts. Put that in the client you have a boolean type set
> to false, while in the server it has been changed to true. The user
> wants to set it to true.
> With autoedit OFF, you have.
> a1) user clicks the "edit button"
> a2) user sees that the field is true, so he does nothing (or clicks
> cancel)
>
> With autoedit ON:
> b1) the user clicks to the checkbox to make it "checked"
> b2) what shold the buffer update do? Get the updated data from the
> server, then process the user input? Or force the user input as the
> right data? But what happens if you change the day of a date that
> someone else has changed before, changing the month?
>
> Just some problems that autoedit brings with syncro with the server. I
> always use autoedit, but have not figured our how to solves this
> problems...
> regads
> Marco Menardi
>
> --- In IBObjects@y..., "pi3k14" <frode@a...> wrote:
> > Could you elaborate on "AutoEdit in apps is generally not a good idea
> > anyway." ?
> > I find AutoEdit to be a nice feature, and refreshing all fields when
> > entering edit state (automatically) shouldn't be that problematic ?
> >
> > sincerely
> > frode