>I have a Custom Object containing library functions that I use as a common routine for all my applications. During its INIT routine, I want to load another Custom Object, that I can later refer to as a separate object. This second object requires routines contained in the calling (first) library.
>
>However, I cannot refer to the library ("oLib") as an object, because the object variable is not yet created. Is there another way to refer to the library object, or do I need to create the second object outside of the library?

Design issues are always interesting. :)

I would go by having an object to hold the most used custom methods. You will be able to load this object at first so it will be available for all the other objects. I usually place those methods in my main object. Since this is the first object, all the other objects will have access to its methods.