Hello Kenneth,

Yes, Garrett is right. Before you issue tableupdate you need to force VFP to
put data in edit mode. The solution for that is as follows.

select (Your alias)

if type("thisForm.ActiveControl")="O"
local loControl

loControl = thisForm.ActiveControl

if pemstatus(loControl,'SetFocus',5)
loControl.SetFocus()
endif
endif

Kaumir


>Try this one:
>Two forms, both subclassed from the same parent class form.
>Both have a two-page page frame. Both use private data sessions, both use the same local view and both have no table buffering. The "only" difference is one form has more controls on it than the other. Control of saving data for both forms resides in the same toolbar.
>
>On one form if you click on a field, edit the field then click the save button, the data is saved. On the other form, the one with more controls, if you don't tab off of the edited field before clicking the save button, the edit wont be saved.
>
>The code to save the edit:
>SELECT theCursor
>= TABLEUPDATE()
>is the same for both forms.
>
>I'm open to ideas as to why both forms behave differently even though they are both so much alike. Something is causing the different behavior, but I'm stumped as to what the difference is. Ideas any one?