Another approach would be to put the "always on bottom" graphic at a higher level than the page (section, chapter, or title level, depending on what your course includes and how universally you want to use it). You could then disinherit it from any pages you didn't want it to appear on. Of course, if you just want it on, say, 3 pages out of 30 in a module, that might not be a time-effective approach.Graphics at the higher level that do not specify "Always on top" will always be below any page-level graphics. This was reinforced for me this week when I was changing my exit-confirmation functionality (see the "Exit confirmation window" thread) and discovered that a title-level "always on top" graphic is trumped by a page-level "always on top" graphic and had to remove "always on top" from my page-level objects to make my exit-confirmation objects appear on top of the page.