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 |
#1
|
|||
|
|||
Implementing database structure
Hello everybody,
I need help on setting the table structure of a DB. I have: Table DocsTbl with fields. DocID DocType DocSubject DocDate Ref.Proc DateProc DocPath DocDispach DocRead Tables DispatchTbl DispID dDocID DispText DispDate DispTo DesinationTbl UserID DispID AccTionTbl ActID ActUser ActDate ProcessNum AcText When a document is registered in DocsTbl, the boss insert a dispatch stored on Dispatch table, and he could insert more than one dispatch over the same document, the user needs to take some action in accordance with that dispatch. How should I establish the relations, taking in attention that one dispatch could concern just to one user or to several users, in this case each user should take an action and store the action and register each action. In the end, the goal is to have trackin on received Docs, each Dispatch that were inserted in a particular Doc, and each action taken by user on each dispatch. As an output shoud have list of entered Docs, Dispatches inserted and actions over those dispatches, each user could chose to see his own actions or all. The scheme is: Entering Doc ---- 1st Dispatch ---- User1 Action ---- User2 Action ----- 2nd Dispatch ---- User1 Action ---- User2 Action hope I was clear enough. thanks all |
#2
|
|||
|
|||
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. |
Thread Tools | |
Display Modes | |
|
|