Search results

Thanks Pat, I've been playing with crosstab queries the past couple of days trying to figure this out. If I get really stuck, i'll be sure to plea for more help.

I've been searching for a good solution for this and can't find it. Hopefully something like this is possible. I need to produce a report in excel from my database that needs to include information from 5 different tables. The relationship between two of these tables is a many-to-many...

Thank You Thanks Pat and Rickster that is what I needed to know. This forum saves the day yet again.

Widow Thanks for the quick response. I checked the cascade boxes on the back end, but when I go to the relationships window on the front end the boxes are unchecked and grayed out so I can't change them.

What is the best way to prevent widowed records? By widow record I mean records in the parent table that do not have a related record in the child table. I have a tblOrder that is linked to a tblProductOrder by the OrderID field. I don't want the user to be able to create a record in...

Thank you both. This has helped me so much. It is so much clearer now. I really do appreciate it.

Thanks for the reply. I have one more question however. I would love to relate tblRep.ExceptionID with tblAgent but won't this "confuse" access? I was under the impression that having two seperate relationships between tables will not work?

First of all thank you for being so patient. Let me try again to be clearer. A rep does not work at an office in the office table. These offices will be customers of the reps. Agents are also customers of reps and they do work at the offices in the office table. An agent is always...

Yes they are both real People. tblRep represents our employees, while table agent represents their customers. And both need to be related to tblOffice. Individual offices are also customers of our reps and Agents work in these offices. I would simply take out the agent to rep relationship...

Doesn't the tblAgent act as this junction table. If I add another one, wouldn't I then be relating tblRep and tblOffice in two ways. And wouldn't that cause problems. I'm sort of thinking that I need to leave it the way it is. This might take some messy queries to get what I want. But I...

I have three tables. tblAgent, tblRep, and tblOffice. I have included a picture to show the current relationships. Normally, an office will be associated with only one Rep. When we start dealing with a new office, a single rep is associated with that office. However, occasionally reps...

Thanks for all your help Pat. I was obviously more then a little confused, but you really straightened me out. It all seems to be working great. I did keep the relationship between the rep and office tables. Hope that doesn't cause me problems later. I don't think it will. Thanks again.

Ok, I may be confused or maybe I’m being confusing. Please bear with me. In the first response you mentioned that I need to make officeID and repID unique indexes in the relation table, which I assume means indexing the field and choosing no duplicates. However, there will need to be...

Thanks Pat, I think you pointed me back in the right direction, but I still have some questions. I think I can now delete officeID from the Agent table, but am not sure if I’m missing something? Also I’m not sure how counting repid in the relation table will allow me to pick out the...

Ok, I have a problem. I am creating a customer database, with the tables tblRep, tblAgent, and tblOffice. Each agent is assigned to one rep and one office. However, each office can have more then one rep and each rep may have more then one office. Now after saying that, in general an office...

Thanks Dave, That worked perfectly.

Thanks for your responses, I got that problem fixed. But now have another problem. As you can see in my code, i use a check box for one of the criteria. Well, with this code if the check box value is zero. OR not checked, then the isnothing function returns, nothing and the following code...

Dave, Thanks for the example it works great for me except one thing. What if i have to use the "or" operator. For example, i am using this on a customer database, where the user might want to limit the results by multiple offices. Underneath I have posted the code that i'm using. Now when...

This would be a one:many relationship. With customers being one and bookings being many. This means that one customer can have many bookings, but the individual booking relates to only one customer. If however, a booking can relate to more then one customer, then it would be a many:many...

Thanks for the reply Pat. I thought I was getting by the autonumber problem, by using AgentID along with the autonumber to create the key field. If I am just using a sequenced number wouldn't I inevitably end up with duplicate numbers, because all four programs run separately?