developingprogrammer
asked on
data modelling best practices
guys, this question is an offshoot of another question titled "No primary key for table benefits". the discussion there skewed off into data modelling and thus here is a question specifically for that. JDettman and Bitsqueezer made some significant, significant contributions there in terms of helping us understand data modelling and a few other things about access memory etc, so be sure to check it out!
ok so let me start my question proper! = )
Bitsqueezer, here's your post below
thanks for your lengthy and very comprehensive response first and foremost!! = )
1) what is the difference database model and database schema?
2) could you touch a bit more on what you mean by
this database is mainly a workflow database which 1) automates work through VBA, 2) as it does the work it triggers custom events which log the work by codes for example H:ACT-R standing for home, account, reconciliation or other codes like that.
i know it might be a bit vague, but am happy to clarify where needed! and thanks so much once again in advance for all your help on all my questions!!
DMS-Cerebro---SSB---Recon.mdb
ok so let me start my question proper! = )
Bitsqueezer, here's your post below
Hi,
I've sorted the chaotic data model a little bit in the attachment. You should always try to create a data model without crossing lines as good as possible, makes it more readable.
Although your model looks a little bit better now I would say there are significant errors in the relations because multiple tables are linked together on multiple ways which mostly is not needed. But I cannot say more because I really cannot see what the target or sense of this database should be.
Moreover I think it would get far away from your initial question to discuss your data model in this thread.
For your other questions about the background of what is saved in pages I think Jim can answer that better than me.
Cheers,
Christian
thanks for your lengthy and very comprehensive response first and foremost!! = )
1) what is the difference database model and database schema?
2) could you touch a bit more on what you mean by
multiple tables are linked together on multiple ways which mostly is not needed? which tables in the attached database are we talking about and what are some fixes for that?
this database is mainly a workflow database which 1) automates work through VBA, 2) as it does the work it triggers custom events which log the work by codes for example H:ACT-R standing for home, account, reconciliation or other codes like that.
i know it might be a bit vague, but am happy to clarify where needed! and thanks so much once again in advance for all your help on all my questions!!
DMS-Cerebro---SSB---Recon.mdb
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
hang on guys!! i think i got it!! here's my new relationship model haha = ) whaddayall think? = ))
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yup yup okie so
1) a code defines an activity of work a staff does. this code typically has 3 categories - cat 1, cat 2 and cat 3. in each category they can have an acronym. for example H:ACT-E stands for housing, account, enquiry. the colon and the dash are just delimiters
each code has a minutes of work awarded to it and also when the process was last reviewed to make sure it is optimised.
2) each code has a container. a container can only have 1 code. and a container can have a super container, and that container can have another super container etc.
3) each code also has tasks which usually must all be completed for the code to be awarded to the staff.
1) a code defines an activity of work a staff does. this code typically has 3 categories - cat 1, cat 2 and cat 3. in each category they can have an acronym. for example H:ACT-E stands for housing, account, enquiry. the colon and the dash are just delimiters
each code has a minutes of work awarded to it and also when the process was last reviewed to make sure it is optimised.
2) each code has a container. a container can only have 1 code. and a container can have a super container, and that container can have another super container etc.
3) each code also has tasks which usually must all be completed for the code to be awarded to the staff.
ASKER
ok i've got an updated screenshot! = )
ASKER
ok guys, i think i've more or less got it nailed. the database schema and also the whole organisation of code. here's the schema and the database = )
DMS-Cerebro---SSB-Recon.mdb
DMS-Cerebro---SSB-Recon.mdb
ASKER
guys thanks for all your help so far!! = ))
ASKER