Commit row in form
I placed combo boxes using separate queries for Row Source.
When I try to input data I can not. Error statement says the row is not committed and that I sould commit the row.
What does that mean? I cannot find a reference anywhere to help correct the problem
Thank you for taking the time to report an issue.
What's wrong... Please write below.
However, when I add a new record to the subform (repairs table), and type a date in the RepairDate field, I get the message "The value cannot be added to this new row until the row has been committed. Commit the row first, and then try adding the value."
but the only answer I found was "The subform row is being saved without a required field, probably the primary key."
How do I commit the new row? How do I enter the primary key, which is an autonumber field added when an entry is made in the row?
Now I am developing this clone of that records list form, to be used in a subform context on another main form. It will be known via a different name this time to receive the callback upon successful commit of the INSERT/UPDATE.
I am thinking to make this record list / add+edit dialog handshake unique in that the list form will pass some sort of token to the add/edit dialog in order that it know who called it, thus know who to send the requery event to when it has successfully committed.
Is that sort of information (which form opened another form) available automatically? Or do I need to pass it along myself when the child form is opened?
I would really like to be able to provide either a simple progress bar or if I could actually show whats going on.
I don't see any way to trigger the VBA code on a row-by-row basis as the form is being painted.
Does anyone have a technique to do this or do I have to go to some other form type to do some dynamic formatting?
update items statement
inset order statement
select @@identity statement
select * from items where statement
My first question is should we put the two SELECT statements inside or outside commit trans?
My second question is do we need a transaction for just SELECT statements like the following?
select 1 statement
select 2 statement
select 3 statement
I think only action queries can be a transaction.
What I would like to do is create a command button that deletes a row from the underlying table. I would like the row being deleted from the underlying table to be based on a control in the form.
but I would really like to learn how to delete a row from the underlying table so that I can use it for other purposes.
NOTE: The PrimaryKey is a replication ID- Any way to get around the error that comes up on the findfirst method?
Am I way out in left field? I saw where I can change row colors in tables. I am running Access 2007 on Windows XP SP3.