help with form and error msg Add Or Change A Record Because A Related Record Is Requi

miken5678

Registered User.
Local time
Today, 15:54
Joined
Jul 28, 2008
Messages
113
This is one of my bigger dbs that i have created. Most contain one to two tables without much issue as the form has always referenced one table. I think my issue arises from the table being empty and trying to save so after trying to force a null value the error still pops up. Is there a correct way to do this besides vb script ( which i have no clue about) so that the form can save without any values in one of the tables? I could be cheap and make 20 tables one for each form but i figure that will kill the db size but solve the null value issue. I assume there is a vb way of population every table off of the policy number once entered within the form?

any help is appreciated. You have to love it when work throws a last minute project on you that youve never really had to deal with before.

thanks in advance
 

Attachments

i also tried changing the direction or way you draw the connection from the child to the parent table with no luck there either.
 
The error you mention is caused due to a relationship between two tables in your db. You are trying to add a child record with no parent record. To stop the error you need to choose not to enforce Referential Integrity on the join. But it seems to me there may be a flaw in you db design if you have a child record with no parent.
 
I assumed i would need referential integrity on the join for the tables so that if an item had to be amended or say the comments field was amended that there would not be an issue. Although no data will ever be deleted from these tables. The parent table is the header table. Also at the top of the form. This error pops up while using the form for any empty table. So this means that every table i have setup has an issue?
 
to give you an idea of what they were initially using i have attached an excel spreadsheet.

there are 20 versions of this form each with slight differences. I am not sure if i normalized the db in the correct way as it seems i drove the db off of the form.. hope this gives some insight as to what i am trying to do.. this will end up being a multiple user fe/be input setup.. hopefully
 

Attachments

Users who are viewing this thread

Back
Top Bottom