Leveling Based on Priority = Overalocation?

[rbryn]

I have 23 projects that utilize the same resources. I have one
project that oversees them all and links to the 23 sub projects. I
can't seem to get project to manage the resources properly or I don't
understand how leveling based on priorty works.

Project 1 = 500 priority, Constraint = As Soon as Possible
Project 2 = 600 Priority, Constraint = As Soon as Possible
Project 3 = 1 priority, Constraint = As Late as Possible

I want Project 2 done before Project 1 and Project 3 being done last.
Unfortanly I set them up in the reverse order and no matter what I do
Project 3 won't release the resources to let Project 1 get them
earlier.

I'm leveling Automatically by "Priorty, Standard"

 

[Steve House]

By scheduling Project 3 for as late as possible, the leveling engine is
presented with a conflict. Leveling ASAP tasks delays work but leveling
ALAP tasks moves them earlier. You want it to occur later but project wants
to make it earlier to resolve the resource overallocations. Try setting it
to a normal schedule from project start with the tasks ASAP and see if that
helps. By having the lowest priority it will still be the latest of the
three projects. And if it's any consolation, it is generally a very poor
idea to schedule from finish date anyway - it makes every task critical and
gives you a schedule with no 'wiggle room' to absorb the inevitable delays
and under-estimations.