>I probably wouldn't use it to define the object reference name of the app object, but for APP_CLASS and APP_CLASSLIB, yes -- to allow the flexibility to swap out a class and/or classlib with just a changed entry in the .h file (or in the main prg) without having to change every place in the code that instantiates it.

I understand that, but for the App Object? You should only have that set once in the App.

The way the framework I use that works is, there is an App class stored in a VCX. The oApp object is intanciated in a framework PRG, from a class defined in code (usually a sublcass of the VCX app class, but doesnt have to be) in the small application specific main PRG that calls teh PRG in the framework.

>However, even the object reference name as a constant makes sense in a generic framework where you might already have your own app object scheme that you want to plug into the framework and not break existing code that refers to it by a certain name.

Yeah, but I doubt that would be used successfuly to much, and you'd need to re-write code anywyas.