Empty Lookup

[RuralGuy]

I had to put some dummy data in the tables. Have you done that?

[mikel]

Yes I have.

I also noticed that when I open my Manufacturer table, I have plus signs next to each line that when clicked show me the gages that are linked to that manufacturer. But, your db doesn't have this? Why would mine have it?

I attached my new db.

[RuralGuy]

I also noticed that when I open my Manufacturer table, I have plus signs next to each line that when clicked show me the gages that are linked to that manufacturer. But, your db doesn't have this? Why would mine have it?

If you open the table in design mode and get to the properties sheet for the table with <ALT> EnterKey you will see the SubDatasheetName property set to [Auto] (the default). Change it to [None]. It can speed up your application as well.

You will also see that the ControlSource of the Manufacturer ComboBox is the MfgID field of the RecordSource of the form. You have left your cbo unbound.

[mikel]

Wow, something so simple. I have so much to learn. Thank you so much for your help. If anything else comes up I will let you know.

[mikel]

I have another question. I've been making the changes to my file and so far the query to form method has worked great. But I now need to add another table called Calibration that is linked to the GageID. Up to this point all of the tables I have been adding have been in a 1 to many relationship with the Gage table always being on the many side. But the calibration table now needs to be the many side. I can create it and the other necessary tables and it works just like the Gage table but how do I combine the 2 so when I'm looking at a form for Calibration I can see some details about the selected Gage?

I tried creating one big query with everything included but I can't get it to work. I've also tried creating a smaller query with just Calibration fields and the other tables linked to the calibration table and a few fields from the Gage table but that doesn't work either. My original goal was to have one form with tabs. One tab for the general information, one tab for procedure information, and another tab for calibration information. Since this is all in one form do I need to use one query? Or do I need to forget about the tabs and make separate forms with buttons on each of them that opens whatever form I need at the time?

So, which method is the best to use. One large query for all of it, a smaller one for each (Gage and Calibration) that somehow ties together or something else?

I attached a picture of my relationship view just in case that helps.

[RuralGuy]

Each page on a TabControl can contain a SubForm. This SubForm has its own RecordSource and can be anything you want. The use of one query for all of the tabs is probably not a good idea.

[mikel]

Ok, so I have one query for the main information tab that includes Manufacturer, Procedure and a bunch of others. I created an additional query for the calibration tab. I can add the subform and it works because it only shows the information for the current gage selected on the first page. But when I try to add a calibration record it doesn't work. How can I get it so the subform shows only records for the gage and so I can add new gage records without having to reenter all the gage information?

Using our previous procedure or manufacturer sample, it would be like wanting to add procedures on the same form as viewing them. Is that possible?

[RuralGuy]

The SubForm control (the control that displays the SubForm) has LinkMaster/ChildFields properties. These are used to filter the SubForm records to a value.

[mikel]

Ok, I have those fields filled out so that the subform only displays certain records based on which gage (GageSN) I am looking at, but I still can't add to the Calibration table from the subform.

Would that indicate a problem with my Calibration query?

[RuralGuy]

This link should answer that question.