Saving data to a table

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
 
R

Rick Brandt

Laurel said:
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?
Click to expand...

DoCmd.RunCommand acCmdSaveRecord
or
Me.Dirty = False
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Add a new row in Named Table (Table1) and add data from txtboxes into last empty cells based on header named of the Table1 0
How to force last row to be saved? 2
How to Populate Data from a table to another 0
Can't go to new record 1
Closing a Bound Form without Saving to the underlying table? 1
Requery a sub table 1
Add a line to a combo box? 3
Saving data back to table 4

Top