![]() Only project Unus is picked out as running late. Quer圓’s datasheet summarises the information we require: The latest of the dates assigned to tblActivity.DateTo is later than that tblProject.DateTo.There is a date assigned to the tblProject.DateTo field.These factors determine the condition for a project to be late running: In this section I give some guidance on working your dates to yield this information, considering that sometimes certain of Access's idiosyncrasies can lead to incorrect results if you’re not aware of them. tblActivity.DateTo The date on which the activity is completed or is due to be completed.Ī key piece of data that your database needs to provide is whether a project is on time or running late.tblActivity.DateFrom The start date for the activity, either actual or scheduled.Or you could leave this blank to indicate that the project as a whole is on-going or that the completion date has not been finalised. tblProject.DateTo The scheduled completed date for the project.tblProject.DateFrom The start date for the project.These are some of the ways you could use these: In the table illustrated on this page there are date fields for both tblProject and tblActivity. You’d find this very difficult to achieve if your activities were recorded as free text. Sorting, filtering, analysing and reporting according to types of activity should be straight forward, consistent and accurate.The activities in the look-up are easily made available to the user through a combo box.This would not be the case if you used a note or memo field for the users to make up their own type descriptions for activities The database administrator has control over the choice and exact description of each activity.My reasons for using a look-up table, in preference to putting a free-form text or memo field include in tblActivity, are these: You’ll certainly want to identify the type of activity being performed. In the following, the party is also assigned to the project to identify the party for who the project is being undertaken: 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 |