Value cannot be added to new row until new row has been committed

hunterfan48

Registered User.
Local time
Today, 14:59
Joined
Aug 17, 2008
Messages
436
So...I looked up some info on this, but I can't seem to figure out why it's happening to my form.

So, on my [Transactions] form I am entering a new transaction number.

Let's call it (105)

So, now I click one of my command buttons which will pop up a new form allowing me to enter new cards into my database associated with transaction (105).

The 1st card I enter works great. When I move on to the second card I'm adding to this particular transaction, I go to enter (105) into my Transaction ID field on this popup form just as I did on the 1st. This will tie this specific card to transaction 105. However, now I get this error message that I see in the title line.

My question is, where did this error message come from? How can it be fixed?

And why would it do it on the second card (or new record in my popup form) and not the 1st new card or record? I repeat the exact same process for both of them.

Thanks!
 
So...I looked up some info on this, but I can't seem to figure out why it's happening to my form.

So, on my [Transactions] form I am entering a new transaction number.

Let's call it (105)

So, now I click one of my command buttons which will pop up a new form allowing me to enter new cards into my database associated with transaction (105).

The 1st card I enter works great. When I move on to the second card I'm adding to this particular transaction, I go to enter (105) into my Transaction ID field on this popup form just as I did on the 1st. This will tie this specific card to transaction 105. However, now I get this error message that I see in the title line.

My question is, where did this error message come from? How can it be fixed?

And why would it do it on the second card (or new record in my popup form) and not the 1st new card or record? I repeat the exact same process for both of them.

Thanks!

I wonder if it's becuase you're calling a new form, rather than using a subform?
 
But, here's the deal. After I exit out of these forms, if I go into my table for Transactions, the new record with transaction ID #105 is there saved.

So, then when I go back to these forms when I know the record is saved, it still says the row hasn't been committed.

How can it not be when it exists in my table?
 

Users who are viewing this thread

Back
Top Bottom