Error msg

ICTkirsten

Registered User.
Local time
Today, 23:10
Joined
Jan 3, 2015
Messages
137
can somebody please tell me what this means pleasee :)
 

Attachments

  • customer error.png
    customer error.png
    22 KB · Views: 92
i dont understand it tho... im really inexperienced with access. how do i fix the error?
 
it's telling you that there is no customer detail record with a value of 'customerID'

You asked what it means, that is what it means.

If you want to know how to fix it, without knowing the context in which the error was generated it is not possible to advise more. We're not mindreaders and not familiar with your project.

You have made quite a few posts to this forum so you should know by now that you would get better answers if you provide more information - like how/when/where was the error generated? In a query, a form/report? some VBA?

And provide the code that generated the error - whether it be vba or sql - plus some example data that causes the issue.
 
You need the CustomerID field in both the tblCustomer and tblCustomerDetail tables so you can link the one customer record to the many details. Then both have to be type Long and the one in tblCustomer should be the primary key. In the detail, index the field with duplicates.

You did not give us enough to really help you, such as, where did this happen, in a query, running code, or opening a form?
 
sometimes messages of that nature indicate a corruption. are you getting this on every read, or just on one occasion?
 
sometimes messages of that nature indicate a corruption. are you getting this on every read, or just on one occasion?

This also may happen if a subform links to the main form by a field which is not the main form's Autonumber ! - subform cannot save a record if it contains a reference to a field in a main form which has not yet been inserted.

Best,
Jiri

ETA : it also happens if main form and sub form refer to the same table !!!
 
" subform cannot save a record if it contains a r8eference to a field in a main form which has not yet been inserted."

Not so. If the field is made required in the child record. Otherwise you can happily produce orphans.
 

Users who are viewing this thread

Back
Top Bottom