I have had this issue for the past few years, and I am taking another stab at trying to find out how to fix it. If you care to review the old thread;
The original thread is located here:
https://www.accessforums.net/forms/d...alue-4926.html
... and happen to see something I am not seeing, please comment on it.
This time, as well as referencing the original thread from a couple of years ago, I am showing pictures of what I mean. I have 'blued' out anything that is internal, but the rest is visible.
PMS-Clip01
This is after I open the database, close the switchboard, and then press double-click the "PMS Purchase Orders - Main Form". This defaults to the first purchase order ever written. Notice how if I was to add a line item to the sub-form, that it already has a Task ID entered, and also has the ETA date for this line? That ETA date is taken from the Order ETA date from above.
Form: PMS Purchase Orders - Main Form
TextBox: ordETA
Control Source: ordEta
Format: mm/dd/yyyy
Default Value: =Date()+14
Form: PMS Purchase Orders - Subform
TextBox: ordlineETA
Control Source: ordlineEta
Format: mm/dd/yyyy
Default Value: =[Forms]![PMS Purchase Orders - Main Form]![ordEta]
PMS-Clip02
This is when I advance the record to the last record in the database.
Notice again how the individual line item has the correct ordlineEta that was grabbed from the record's ordEta above.
So with just those things, you would think that all will go smoothly, but this is where it gets 'weird'.
PMS-Clip03
This is when I switch to Datasheet View. Notice how the cursor is highlighted on the ACB. The arrow is indicating that line representing that record we were just viewing in Form View.
PMS-Clip04
Now if I go to ANY OTHER RECORD, in this case, Record of ordId # 10819. This would represent another record, which is another purchase order. So I scroll to a new record that I want to work with.
PMS-Clip-5
When I am in Datasheet View, scroll to a different record, and switch back to FORM VIEW, this is what you get. The individual line item 'ordlineEta' does not grab the current form's ordEta from the record I am working with.
At this point, if I was to add a line item, it would use the date it has set up for me, so I have to change it. I can advance the record forward or backward, and it will show up just fine. It only happens when I do the sequence I described in the five pictures.
It is really odd, and I am ready to try and tackle this issue again.
Tim