L
Laurel
How can I be sure that data in a new row is saved to a table before I issue
a .Requery? That is, if the data is entered, but the user doesn't move to
the empty new row before launching a procedure that does a Requery? The
SAVE method seems to apply to things like forms and table definitions.
Update applies to a SQL statement. Is there a way to force a new row to be
written out?
tia
las
a .Requery? That is, if the data is entered, but the user doesn't move to
the empty new row before launching a procedure that does a Requery? The
SAVE method seems to apply to things like forms and table definitions.
Update applies to a SQL statement. Is there a way to force a new row to be
written out?
tia
las