Search results
-
L
Table Design re one-to-one relationships
Okay, I see what you mean. When you see it then you say "Oh, that's what he/she meant." A year ago I did this with another database (see attached PhoneNumber db) but abandon it because of the constant calls they can't tab from this number to the next or go back. What do you think? -
L
Table Design re one-to-one relationships
I did, but no takers. Anway, how do you do the below? ... I might suggest a form/subform design for data entry of the phone info but then use something different when editing existing customer records; perhaps some controls that use the DLookup() function to pull in the various phone numbers... -
L
Table Design re one-to-one relationships
Do you have any examples I can see? For this particular design I have search for months. Other sites have the same design--basic subform look. Not what they wanted. MS templates look good but the table structure is Phone1, Phone2, Phone3, Phone4, etc. -
L
Table Design re one-to-one relationships
Okay, gotcha. They don't like the look of subforms. The problem is a lot of their databases are using the MS template; they like that look. You know, Home (888) 888-8888 Work (888) 888-8888 Mobile (888) 888-8888 Fax (___) ___-____ -
L
Table Design re one-to-one relationships
Hello MajP and The_Doc_Man, I finally did the database over, but have run into one problem. I need to keep track of each job they send a worker on or to interview for. They want it to be like: 1. Open Company form – enter company information 2. Open Event form – enter events. a. If... -
L
Table Design re one-to-one relationships
Now, I see what's confused me your db. It was the naming--that is, tblCompanyEventMedia. When I saw that I kept thinking about linking tables--Company table and Event table to Media table. -
L
Table Design re one-to-one relationships
Gotcha! I just went back over your db. It's coming back to me. I keep forgetting stuff and have to relearn it. I know this is basic stuff but I was always get stuck in that one area when trying to normalize the db. Anyway, thanks a bunch! -
L
Table Design re one-to-one relationships
Do you have an example of "The other tables containing supplemental data that is not always processed"? I think this is where my confusion lies. Many of the events that will be created will not have to answer information regarding Media or Meeting. That’s why I kept thinking about separate... -
L
Table Design re one-to-one relationships
jzwp22, I got what you did. I was trying to explain my thinking regarding my one-to-one confusion: tblEventTypes is a lookup table. You go: EventDate EventTime EventType (from tblEventTypes) If EventType is media then form opens re media sent If EventType is meeting then form opens re... -
L
Table Design re one-to-one relationships
Okay, maybe I am getting the Event table wrong, which consists of the following: tblEvent EventID EventDate EventTime EventType (i.e., send media, receive mail, phone calls, meeting, any type of activity) EventDescription EventNote Two of the event types will require further questions. For... -
L
Table Design re one-to-one relationships
Gotcha. Regarding "...future event...", I want to keep this db simple as possible. My head is hurting from the others :) Thanks! -
L
Table Design re one-to-one relationships
Yes and no. The future event is not a must, just a reminder. And, those two fields may be deleted. Tracking the media is the most important. -
L
Table Design re one-to-one relationships
Okay, here it is in Access 2000. -
L
Table Design re one-to-one relationships
Attached is what I have so far. I'm not following you on tblCustomerEventMedia. How do I jump to there to enter the quantity? -
L
Table Design re one-to-one relationships
Okay, I never thought about putting Event Type in a separate table. I am just thinking that Event Type goes inside of Event table--that is: tblEvent EventID = pk EventDate EventTime EventType = Number (get the type from a lookup table) EventDescription Let me actually do what you suggested... -
L
Table Design re one-to-one relationships
Yes, one customers can have many events. An event is: cold calling, meetings, preparing for presentations, researching, receiving mailing, sending e-mails, and so on. Basically, any activity going on. After thinking about it some more, I decided I needed one big Event table. (I get cared... -
L
Command Button Wizard not working...
I think I found out the problem. When you have unbound controls with ControlSource filled in, it will not work. If the unbound controls ControlSource is empty, it will work. Meaning, the form with the unbound controls filled in will be blank. See these... -
L
Max date from a concatenated field
I was doing that--that is, 1/1/2010--but he does not want that. What's written must be verbatim. -
L
Max date from a concatenated field
That's the first thing I did, but received error message: Data type mismatch in criteria expression. I assumed bececause it's a calculated field. When the field is empty I get: Error# How shall I handle that?