Access Database Engine Cannot Find a Record

[KLahvic01]

Question.

Why does my database populate this error when I open my form:

The Mocrosoft Access Database Engine cannot find a record in the table 'tblMasterList' with Key matching field(s) 'MasterID'.

But when I click ok on the error message, the database works fine until I try to navigate to a new record. Not sure what is happening here.

Any help would be awesome!

KJL

 

[Sketchin]

Are you certain that tblMasterList has the field MasterID? You haven't renamed anything?

 

[boblarson]

That is a classic error message for your database having a CORRUPT record. What you need to do is to scan down the table's primary key field and look for something with either ######## in it or a bunch of strange looking characters. If it is there, then you make a copy of the database file as a backup and then run COMPACT AND REPAIR and then go back to that table and delete the record(s) which should then have the PK field completely blank. You'll then need to recreate the deleted record(s) if they are important.

 

[KLahvic01]

Yes the field exists, that was the first thing that I checked.

However, the field is part of a relationship and it is used on a form whose record source is a different table (tblCollection). What is interesting is that when I click ok on the record, the functionality works.

Could this be the reason for the error, the field being used on a table with a different record source and being related to the table through relationships?

KJL

 

[boblarson]

Well, if you don't have a corrupt record it may be somewhat related to how the data is related. Hard to say without seeing your relationships and/or database.

Do you have either

1. A single form but it uses two (or more) tables in its record source? If so, then you likely need to move to a main form/subform set up making sure to not have the same tables in both forms.

2. A main form and subform (if so, then the subform should not have, in its record source, the table the main form is using and vice-versa.

 

[KLahvic01]

I figured out that it was simply that both controls were on a form with the same record source and that by creating a subform/main form relationship with parent and child, I got it to work exactly as I had anticipated.

Thank you for your help!