Thanks again gents.
So what you're saying is it really depends on what's in the ESU and not so much on it's size?
Although I'm a bit surprised that if an ESU had an increased .h DSTR that the ESU doesn't then include all the other .hs that reference it. (I used to do a find in files in C++ and redo the typdef for them all and add to the same OMW)
Yes, that was my point - that it really depends on WHAT is in the ESU (as well as every day packages) that should determine if a full is required. I doubt that if a .h file definition changed they (Oracle) would include everything that referenced it - in some cases it becomes a very recursive task to find all true dependencies. Besides even if an ESU did have all referencing objects it certainly wouldn't have any of your custom objects that may reference the changed .h file definition.
....and Brian, Shaun of the Dead, obviously
LOL. In the end I think I would have to agree.