![]() ![]() In the tables above, the party identity relates to the person, group of people or organisation assigned to perform the activity. Whichever of the above schemas you use for your database, this is representative of the corresponding Access tables and their relationships: My experience is that names work well when they imitate their usage in the business for which the database is created. Make your naming convention your own, and title your tables accordingly. You don’t have to use the same terms as I do. If you do, this model still works - all you need do is add an additional table into the schema: If your business does not demand as much detail, you may consider my proposed structure is too top heavy and that this model would be best:Īlternatively, if your project is converting a dumb motorway into a smart one, you may need an extra layer of detail between task and activity. Tables on that page dovetail with the tables introduced here. My Party data model web page introduces the concept of the entity party and how it can be incorporated into a database. I’ll be using the entity party as a coverall for people, groups and organisations. ![]() The module treats an activity as something undertaken by a person, a group of people or an organisation in order to complete a task. ![]() The module reflects this notion of a project: My objective is to provide a general-purpose module to manage who-does-what-and-when that you can incorporate into a database. Microsoft ® Access Database Tables for Project Managementĭata tables and their relationships for a Microsoft Access database for recording who does what and when - for projects, tasks, jobs and activities. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |