If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
Normalization
http://www.box.net/shared/0hedzz7ixh
"June7 via AccessMonster.com" wrote: Click on the link in my post which should take you to my folder on the Box. net site and you should see an Upload button. When you click it should open dialog box that allows you to browse to your file and select it for upload. If my Share box won't work then post link to file in your box and I will download from there. If you signed up on the Box.net site then on the right side of the folder or file is a box that says 'Shared'. Click on it and will open a frame that shows the link url. Select and copy the url string then paste into post here. Be sure to copy the link to the file for me to download, not the folder. Whenever a file is loaded up or down the box owner gets and e- mail. lmcc007 wrote: I sign up, but how do I send it you? If you want to drop your project to this site, will be happy to look at: http://www.box.net/shared/0mfqudj3nz [quoted text clipped - 26 lines] Do you think I need to put job information in a separate table for normalization? Or is it okay in this table? -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200907/1 |
#12
|
|||
|
|||
Normalization
Wow, you put a lot of forethought into this, not building on-the-fly. When
you asked if could upload database I had thought would be actual project to test run. Your summary positions the company as parent, 'For example, if Shell Oil is deleted, I want all the events for Shell Oil deleted as well'. You will not have more than one job per company? I see as the primary purpose is to track job apps and all data contributes info to that effort, so the job record is parent to events, thus recommendation for table with one record per job. Really no need to delete records, use queries to filter output. But just one opinion and am not an expert, just another user who learned because project thrown at me at work and then another and another and another.... lmcc007 wrote: http://www.box.net/shared/0hedzz7ixh Click on the link in my post which should take you to my folder on the Box. net site and you should see an Upload button. When you click it should open [quoted text clipped - 14 lines] Do you think I need to put job information in a separate table for normalization? Or is it okay in this table? -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200907/1 |
#13
|
|||
|
|||
Normalization
I've been studying MS Inside Out 2000, 2003, and 2007. And, it suggests
doing it on paper first. I haven't figured out the flow chart part, but before I was laid off I would notice the programmers would do and use flowcharts. "June7 via AccessMonster.com" wrote: Wow, you put a lot of forethought into this, not building on-the-fly. When you asked if could upload database I had thought would be actual project to test run. Your summary positions the company as parent, 'For example, if Shell Oil is deleted, I want all the events for Shell Oil deleted as well'. You will not have more than one job per company? I see as the primary purpose is to track job apps and all data contributes info to that effort, so the job record is parent to events, thus recommendation for table with one record per job. Really no need to delete records, use queries to filter output. But just one opinion and am not an expert, just another user who learned because project thrown at me at work and then another and another and another.... lmcc007 wrote: http://www.box.net/shared/0hedzz7ixh Click on the link in my post which should take you to my folder on the Box. net site and you should see an Upload button. When you click it should open [quoted text clipped - 14 lines] Do you think I need to put job information in a separate table for normalization? Or is it okay in this table? -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200907/1 |
#14
|
|||
|
|||
Normalization
No, there may be several jobs per company. For example I have applied with
Shell Oil several times: Date EventType JobTitle Notes 1/1/08 SubResume Administrator 1/1/08 Email recd Administrator Confirmation ltr 2/1/08 SubResume Admin. I 2/1/08 Email recd Admin. I Confirmation ltr 5/5/08 SubResume Admin. II I think I have worked at this too much I am confusing myself. But I have a JobTitle table that is a list of job titles. Now, I am thinking about doing a JobTitleInfo table that gives information about each job I applied for. That's where I am confused on whether I should do this. "June7 via AccessMonster.com" wrote: You will not have more than one job per company? I see as the primary purpose is to track job apps and all data contributes info to that effort, so the job record is parent to events, thus recommendation for table with one record per job. |
|
Thread Tools | |
Display Modes | |
|
|