View Single Post
  #2  
Old May 15th, 2009, 08:39 PM posted to microsoft.public.access.tablesdbdesign
Fred
external usenet poster
 
Posts: 1,451
Default Implementing database structure

These are hard to describe, as evidence by a quandary posed by your post.

Your inquiry was asking for help on a table structure, yet half of your post
gave a table structure as "information" . If it's right, then you have
already answred your question, and if it's wrong, then it is not an
information source. So, what are we supposed to do with it? :-)

- - - -

I think that you will need rigorously define / clarify for yourself or us
the relationship between dispatches and user actions, if there is one. In
some cases, in the sequence, the user action is preceeded (initiated?) by a
dispatch, and, in other cases, a user action is preceded( initated?) by a
user action. If there truly is a causal / sequential relationships
between user actions and dispatches, then thsoe will be related to each
other. If not, then those are just different types of events related to
registered documents.

Also, how lengthy do the scenerios get? How many dispatches can there be
per documetn, and how many users can there be fo one dispatch. If the answer
is "unlimited" that's fin, it just needs to be know for table structure
design.