Subject | Re: [IBO] Posting |
---|---|
Author | Paul Vinkenoog |
Post date | 2003-09-03T12:36:16Z |
Hi Gediminas,
- Because you change data yourself, in code - e.g. in an event handler or
another procedure.
Wherever you do this, you call Post yourself when you're done with the
record.
- Because the user changes data, e.g. through a TIB_Edit or a LookupCombo.
In that case, the most logical thing is to let the user confirm the
change by clicking a button. The TIB_UpdateBar is great for this, I drop
one beside almost all my Grids and/or clusters of data controls.
Talking about grids, the default behaviour is to automatically post when
the user scrolls away from a changed record.
To help the user not to "forget" posting, I set ColorScheme true on
almost every user-visible query.
Things being like I described above, you rarely need NeedToPost, except
maybe if a dataset closes and you want to inform the user that there are
"unsaved" changes.
Greetings,
Paul Vinkenoog
> What is the best way to check if dataset is changed & needs to be posted?In most apps, data are changed in one or two ways:
> I have tried HaveToPost in Lookup relation, but this atribute gets true
> even if dataset isn't changed :-/
- Because you change data yourself, in code - e.g. in an event handler or
another procedure.
Wherever you do this, you call Post yourself when you're done with the
record.
- Because the user changes data, e.g. through a TIB_Edit or a LookupCombo.
In that case, the most logical thing is to let the user confirm the
change by clicking a button. The TIB_UpdateBar is great for this, I drop
one beside almost all my Grids and/or clusters of data controls.
Talking about grids, the default behaviour is to automatically post when
the user scrolls away from a changed record.
To help the user not to "forget" posting, I set ColorScheme true on
almost every user-visible query.
Things being like I described above, you rarely need NeedToPost, except
maybe if a dataset closes and you want to inform the user that there are
"unsaved" changes.
Greetings,
Paul Vinkenoog