GG --
You would need to do several things to accomplish your goal:
1. Create a master project consisting of all projects in the database,
apply the Resource Usage view, and save it in the database.
2. In this master project, copy the resource Work table and name it
something like _Overallocation. Add/delete columns to include those you
have specified (except for the Overallocation Work column, which does not
exist in the system).
3. Create a new Group and name it something like _Overallocated. Specify
the grouping by the Overallocated field in Descending order.
4. Copy the Resource Usage view and name it something like _Overallocated
Resources. In the View Definition dialog, select the new Table created in
step #2 and the new Group created in step #3 and then apply this new View.
5. Right-click in the timephased grid and select the Overallocation field.
This will meet your criteria to see the amount of overallocation on each
assignment.
6. Collapse the Overallocated: No grouping.
7. Save the master project.
Whenever you open this master project, you can apply this view. Just a
thought. Perhaps the others have some ideas, too.
By the way, Project marks a resource as overallocated when the resource's
Peak Units value is greater than the resource's Max. Units value. For
overallocated resources, it then sets the value in the Overallocated field
to Yes. Hope this helps.
--
Dale A. Howard [MVP]
Enterprise Project Trainer/Consultant
Denver, Colorado
http://www.msprojectexperts.com
"We wrote the book on Project Server"