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