Search results

A lookup field is set up in the table using the lookup tab in the lower pane of the table design view. Having lookups at the table level is generally not recommended. This site provides details Using the query and creating a single form will work fine for displaying but it won't work for...

There can be only 1 PK per table unless you have created an index involving all three fields and are using that combination as the primary key. Out of curiosity, are the driverID and unitID in the junction table set up as lookup fields?

I don't know what version of Access you are using, but the following directions to hide the system tables should apply to Access 2007 and newer. Go to File-->Options-->Current Database. Scroll down to the Navigation section and click on the button: Navigation Options... Under the section for...

No, do not remove them. Those are system tables. Usually they are hidden. I believe I toggled a setting to show them. I'll post back with directions to hide them.

You're welcome. Good luck on your project.

Unfortunately, pulling an image into a form is not something I've ever done before, so I would not be of much help there. I would suggest that you start a new thread with that specific topic. Someone on the forum has probably done something similar.

Which query is the aggregate query you referred to in your earlier post?

You're welcome.

I would typically use a main form based on the order table with a subform based on the tblOrderDetails. In that subform, you would use a combo box for the components (the combo box would be based on the components table)

Following the rules of normalization, if an order can consist of more than one component then you should set up your tables to handle it now. This is what the basic structure would look like: tblOrders -pkOrderID primary key, autonumber -fkCustomerID foreign key to tblCustomers -dteOrder...

You're welcome.

Yes, there is an easier way: a third table that relates the performances and tickets or more correctly the seats. The third table will be the ticket table. See the following 3 tables: tblPerformances -pkPerformID primary key, autonumber -PerformanceTime -PerformanceDate -ProductionCost BTW...

Can you provide some more details on your tables?

It sounds like something else might be at fault. Is there any chance that you can post your database with any sensitive data removed or altered? Do you import the information from your AS400 system into an Access table or are you using a linked table?

Have you set the query to return unique records or unique values only? From the design grid view open the property sheet for the query and set the unique records property or the unique values property to yes. In SQL text, you would just need to add either DISTINCTROW (unique records) or...

Because you use the material table twice to join to the manufacture table, you typically have to create a query that pulls the list of materials used as raw materials first and then join that to a query that pulls the finished goods. In those queries, you have to rework the joins between the...

When I did item 2 as you described the name showed up just like it did with item 1. You could also make the student name appear by hitting the tab or enter key after entering the studentID number. I took care of item 3 in the attached. As to item 4. I would recommend a separate functionality...

OK, I think I have the code doing as you described in your earlier post. The revised database is attached. I took a quick look at your tables, and I do see some areas for improvement, but keep in mind that if we change the table structure, all your existing queries, forms and reports will not...

The labor & other costs associated with producing a material would most likely be in a separate but related table. That might actually be more straight forward than the bill of material aspect.

Yes Your example table looks correct. The manfID will just be sequential numbers (unique record identifiers). That's where things can get a little tricky. For one level down you should be able to use a subreport embedded in the main report, but if you want to break it out past that second...