Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Database Design / April 2005

Tip: Looking for answers? Try searching our database.

do things look normal?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
justin - 11 Apr 2005 20:01 GMT
I just wanted to post my tables and their relationships to
get some feedback from the pros on whether or not this
database is headed in the right direction. Thanks for the
help in advance.

tblcontractinfo
 DocumentID (autonumber) (primary key)
 Documenttype
 documentname
 CSFScontactname
 CSFSprojectcontact
 CSFSoffice
 OtherPartyContactName
 AccountNumber
 POnumber
 DollarAmount
 DocumentActive
 Enteredby

tblcontractdates
 DocumentID (primary key)
 recieveddate
 startdate
 enddate
 routedate
 routecompletiondate

tblcomments
 ID (primary key)
 comments
 date
 name

tblcontracttype

tbloffices

these last two tables are used as drop down menus on the
form.

The DocumentID fields in the tblcontractinfo table and
tblcontractdates table are related in a one to one
relationship. The ID field form the tblcomments table is
related to the DocumentID field in tblcontractinfo table
in a one to one relationship as well.

Well that's it. What do you think? Thanks for the advice.

-justin
Duane Hookom - 12 Apr 2005 05:06 GMT
I don't care for:
   tblcontractdates
     DocumentID (primary key)
     recieveddate
     startdate
     enddate
     routedate
     routecompletiondate
I would expect as soon as you deply this application, some pointy-haired
boss will need to track another date which will cause redesign of tables,
forms, queries, reports,...

A more flexible solution would have a table like
   tblContractDate
   DocumentID
   DateType
   EventDate

Then add a table of date types for a lookup.

Signature

Duane Hookom
MS Access MVP

>I just wanted to post my tables and their relationships to
> get some feedback from the pros on whether or not this
[quoted text clipped - 45 lines]
>
> -justin
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.