Access Engine Could not find key matching field error

hrdpgajjar

Registered User.
Local time
Today, 06:06
Joined
Sep 24, 2019
Messages
115
HI all,
i am trying to create a simple order system. done all relationship and sub form matching field. but still got error as per attachment. I am trying to learn this thing so pls guide me what i am doing wrong. I have attached my database and query screenshot.



Thank You,
 

Attachments

  • Purchase Order System.accdb
    Purchase Order System.accdb
    1.2 MB · Views: 11
  • error.png
    error.png
    16.8 KB · Views: 24
non of the queries generate an error - suggest advise how to replicate the error
 
Open your View Customer Form and test it.
Thanks for the effort. why it is not working as i need? i mean to open "View Customer Form" And add products on subform? what is the problem doing it?

You can take a look at the file i have made earlier,



it works in my FDMS File but not work here. what exactly is the problem ? or it is just access bug?
thanks
 
Order Detail Table needs that an OrderID must be found in Order Table (which must be open since you have Linked fields there).
Did u take a look at the FDMS File i have attached? i am trying to do the same thing here, but not worked? what is wrong?
 
You have not attached a file, you have provided a web link
. And have you tried Arnel's suggestion - in essence you have too many tables in your subform query
 
You have not attached a file, you have provided a web link
. And have you tried Arnel's suggestion - in essence you have too many tables in your subform query
my file size is too big to attach here, so i've shared it via media fire. Ofcourse i've tried Arnel's suggestion but its not what i want.
 
Now cross posted here
 
my file size is too big to attach here, so i've shared it via media fire. Ofcourse i've tried Arnel's suggestion but its not what i want.
Hm. "...not what I want."

Sometimes, when working with a relational database, we have to relinquish "what we want" and adopt "what actually works". The nature of relational database dictates what is, and what is not, effective.

Is that possibly the case here?

I am referring to the subform design in which you have multiple tables in the query which is the recordsource for a subform.

As a general principle, for data entry purposes, forms and subforms should be based on tables or on queries with one table when possible. The more complex a query becomes, the more likely it is to fail as a recordsource for a data entry form or subform.

I suggest you take a look at the alternative ArnelGP offered.
 

Users who are viewing this thread

Back
Top Bottom