newbe question

[jackley]

Hi there,

Sorry if this has been covered, i could find it anywhere.

I'm very new at this and this is my first Database.

I've created a task data base for my work.

Basically what I want is to be able to show how many days/Mb are left to complete on a per project and per priority basis.

The project and priority are set by selecting from a value list pop up menu.

So something like:

Project A has 200 days of high priority tasks left, 100 med tasks and 300 low priority tasks.

Then something similar for the memory lists.

I hope that makes sense?

james

[email protected]

[BruceJ]

I assume you have two tables:

1. Projects

2. Tasks

See my attached.

In the Projects table, create three key fields that will each auto enter the "priority" levels you are using to classify the tasks. Then create three relationships using a combination of the newly defined key field above and the unique project ID.

You should now have three additional relationships, each only connected to a specific priority level and the tasks. Now, add three calc fields in the Projects table that uses the new relationships the SUM the tasks days.

Hope this makes sense. I've attached a simple version becasue I'm not blessed with being very articulate about these things.

Projects.zip

[jackley]

Thanks so much for the response Bruce.

I tried to get my head around what you sent, and I may understand it. But I think I may have made it difficult or impossible with the way I've get it set up?

I don't suppose you could look at an empty version of my db and tell me if it's too much work to do what I want?

I haven't set up any relationships at all, all my fields are in one table.

The projects overview layout is the one I'm trying to get this data in.

Thanks again for your time.

james

AudioTasks_copy.fp7.zip

[BruceJ]

I'd be glad to.

It looks like a nice clean interface and very simplified.

I need some info though:

Q1: Am I correct in assuming that each project can have many tasks?

Q2: Each task is only applicable to a single Project?

Q3: Do you want to have a lot of various projects, or just the three in the drop down box (Echo, Yeti, Loki)?

Q4: Does each TASK have a specifc Mb and Time or is it the PROJECT that has the specific Mb and Time?

[BruceJ]

OK.. I played with it. You can use the same structure and use a Self-Relationship to do the same thing. I think that you'd be better off with two tables though and not have to mess with the auto-enter thing that may lead to data entry error.

I've added three relationships and SUM fields along with three auto-Enter key fields to base the summaries on. Note that each to see the updated sum of days for each level of priority, the record must be commited by moving to another record or clciking into a non-field area.

Let me know if this makes sense. Again, if it were me, I'd use two tables for this.

AudioTasks_copyz.zip

[jackley]

Ok Bruce you are the man, thanks so much for the help!

Q1: Am I correct in assuming that each project can have many tasks?

A:Yep, each project could have a lot of tasks.

Q2: Each task is only applicable to a single Project?

A: Yep, each task goes with its own project.

Q3: Do you want to have a lot of various projects, or just the three in the drop down box (Echo, Yeti, Loki)?

A: Just the 3 projects.

Q4: Does each TASK have a specifc Mb and Time or is it the PROJECT that has the specific Mb and Time?

A: Each task has a specific Mb and time.

The version you posted does exactly what I need, except:). I'd like the project (Loki, Echo, Yeti) to be a factor as well. So, I can show the remaining days and Mb per project. If you look on the "Project Overviews" layout you can see the where i started to set this all up.

I see your "Sum(Needed::Projected Time)" and thought I could just make a new field and add Loki in there somewhere, but I can't get that to work.

Thanks again for all your help. I think once I get this working I'll understand the whole thing much better.

James