Search results

If I click on the ... button in source in the form's properties, I get a window similar to the query builder. Is that what you meant? I can add the table there, and the existing relationships come up. Oh, and then I can add the field. Awesome!

I've been using a table as the source for the report. My IncidentDetails table, to be specific, since it has the involved ProductID, Quantity, and CategoryID. They're probably the main three items I'll need displayed. Is it customary to build a query first to use as the basis for a report?

My next question is about reports, and although I realize that means it should go into the Reports section of the forum, you guys are already somewhat familiar with my layout and level of skill, so I'm just going to reply here rather than start another thread. I've built my first report...

I use the same combo box because it's part of the sub-form / sub-table that allows me to enter multiple products for each Incident (main table) record. After reading your reply I realized that if these text boxes were part of the subform, as I create a second record it would add a second set of...

The thought of getting to code something is very tempting. Unfortunately as it's the combo box that I'm going to be using five to ten times per form now, it won't make for a very pretty form. Maybe I'll just un-hide the item number / ProductID and have it use that. At least then it's specific. ^^

Great! One more little issue I've had since setting up this forms. I think it might just be the way it works, but I figured it can't hurt to ask. When I drop down the combo box for Products, it lists my products based on five fields. ProductID, which is our in-house item number, and which I...

Oh nice! Good to know. I'm excited to maybe get to a point where I get to write some actual code. I went into this thinking there'd be some fairly heavy coding involved, but so far it's all so graphical... I suppose that's a good thing! Now that I've got this form nailed down, I'm able to...

Well it's coming along great. I have changed a few of the ways things are stored in my main tables now... I had been having it store Country name in my main Incident table as an example. I'm not sure why. Everything is all ID now and related properly, I think. I have a question about queries...

Wow, when I created the form with sub-form via the Form Wizard, it automatically created the IncidentProductDetails form for entering multiple Products involved at the bottom, and it also assigns the IncidentID to match the new Incident record that I'm creating! I didn't think it would be quite...

Wow, when I created the form with sub-form via the Form Wizard, it automatically created the IncidentProductDetails form for entering multiple Products involved at the bottom, and it also assigns the IncidentID to match the new Incident record that I'm creating! I didn't think it would be quite...

Wow, when I created the form with sub-form via the Form Wizard, it automatically created the IncidentProductDetails form for entering multiple Products involved at the bottom, and it also assigns the IncidentID to match the new Incident record that I'm creating! I didn't think it would be quite...

Well I'm plodding along and thought I'd post an update. I got Incidents and IncidentDetails separated into two different tables, and created the relationship between the IncidentID that each contains. I haven't attempted to create a form yet that will allow me to enter them, I'm still working...

Wow, that was a lot about queries. I have a series of video tutorials that I'll have to run through again. I think there were four or five about queries. Luckily, at the moment, I don't have any incidents that are identical, at the moment. I saved all of the ones with multiple product...

Now, the only problem I foresee is the 400 entries I've already made. They have the items listed in the incident table already. Can I migrate them to this new ProductsInvolved table? Or should I create a new "Incidents2" table, copy the data I want into that one, and then create my...

I think I am starting to see what you mean. My existing Incident table will still contain CustomerName, ComplaintDetails (memo), but will link to a seperate table that will list the Product (which links to the Product table), lot number and a field I use called ComplaintType which is just a few...

Yeah, some of it seemed a little backwards when I was making it. 1. Yes, customers can make more than one complaint, but in the 400 Incidents I've entered, I've only come across one duplicate. 99% of them are from consumers. The Distributor and Store that I enter is basically for tracking back...

Sorry, and I should go on to say that I know it seems like there is a little redundancy there, but due to the information that I'm actually given on these Incidents (which I hope to change in the near future) I often have to leave some fields blank. Example: CustomerName in the Form/Incident...

Sorry, I should have listed it a little more thoroughly. My main table is the tblIncident. It contains a UniqueID that's just a simple numerical increment. I have other tables for: Products (the unique key being our in-house item number from our accounting dept), Distributor, Store, Country...

Hello! I'm very new to Access and have only just recently set up a small database for our customer complaints. It's pretty bare-bones; there is an "incident" table that has fields for customer name, phone, product, etc. The ProductID field is linked to a ProductID key field in another table...