OK, so I've been looking at your dB.... First thing is ...I hate macros!!
What is happening is that when you open the Action Items form, a macro copies the "borrower" id in the Project form to the unbound text box, then copies the "Loan_ID" in the Project form to the projects unbound text box (naming problems) in the Action Items form.
Then another macro copies the the "Loan_ID" from an Action Items sub form to the projects unbound text box on the Action Items main form.
Since there are no action item records for the Borrower and project ("Loan_ID"), the value in the projects unbound text box is wiped out. So when you try to add a new action item record, there is no project ("Loan_ID") available to create the record.
I can't fix it using macros. I don't use macros (ever) and don't want to learn, so.....
Fixing this using VBA code would be fairly easy. How are your VBA skills??
----------------------------------------------------------------------------
Not trying to slam you, but I see things that I think will cause you problems....
In looking at your dB, I did notice many other problems that I would suggest you attend to before moving on.
Every code module should have two lines as the top two lines:
Code:
Option Compare Database
Option Explicit
There are spaces and special characters in object names. example bad field name: Borrower Tier (New vs# Old - Variance)
There are fields that begin with a number : 85% CH Flag
Some suggestions:
Use only letters and numbers (exception is the underscore) for object names.
Do not use spaces, punctuation or special characters in object names.
Do not use look up FIELDS, multi-value fields or calculated fields in tables.
Do not begin object names with a number.
There are a few reserved words used as field names: example "Year" and "Month"
http://www.allenbrowne.com/AppIssueBadWord.html
You might also look at
Microsoft Access Tables: Primary Key Tips and Techniques
http://www.fmsinc.com/free/newtips/primarykey.asp
Autonumbers--What they are NOT and What They Are
http://www.utteraccess.com/wiki/Autonumbers
AutoNumber
Purpose: Use an AutoNumber field to provide a unique value that serves no other purpose than to make each record unique. The most common use for an AutoNumber field is as a primary key.
Linking problems (IMO)
And speaking of tables..... "tbl_kpi_calculations" has 254 fields!! I've never seen that many fields in one table......