I guess my problem with this is having a field as a control source. I can
envision modifications being made to a table, the user getting some kind of
error in the lostfocus and just canceling out of the form. Now a record has
been updated in the table but the user thinks he cancelled what he started.
No wonder I don't use fields as controlsources.
Jerry Cotton, MCP
2nd Marine Aircraft Wing
Management Training and Assistance Team
Cherry Point, NC 28533
(252)466-4854
mailto:cottonjp.ctr /AT/ 2mawcp D.O.T usmc.mil
> -----Original Message-----
> From: Ed Leafe [mailto:ed@leafe.com]
> Sent: Friday, October 31, 2003 9:57 AM
> To: ProFox Email List
> Subject: Re: Restrict Textbox Values?
>
>
> On Friday, October 31, 2003, at 09:48 AM, Cotton Mr Jerry P wrote:
>
> > Let me get this straight. You're saying that the data gets
> written to
> > disk
> > in the Valid and that you can't revert it in the lostfocus.
> Are you
> > saying
> > that you would allow code to prevent a control from losing
> focus but
> > the
> > data was already written to disk. Doesn't sound to kosher to me.
>
> If valid returns .T. or a non-zero numeric value, the
> ControlSource is
> updated with the contents of the control at that point. If the
> ControlSource is a field in a cursor, that field is updated
> then. With
> buffering, LostFocus could possibly revert it to its original
> unchanged
> value, but it is severely limited - it can only revert or accept. If
> there was an intermediate value, it's gone by the time LostFocus()
> fires.
>
> ___/
> /
> __/
> /
> ____/
> Ed Leafe
> http://leafe.com/
> http://opentech.leafe.com
>
>
[excessive quoting removed by server]
©2003 Cotton Mr Jerry P |
