>>I'm just exploring some of VFP's foundation classes. I ran across this:
>>
>>

>>In app.h is this:
>>#DEFINE ERROR_IN_ERROR_METHOD_LOC    "Error in error handler"
>>

>>As far as I can find it's only used in one place in _error class.
>>
>>What's the point of defining something in an include file that only gets used once?
>
>Also, you can define any constant which you currently use, perhaps, only once - or even not at all! - with the idea of, perhaps, having more instances later.
>
>For instance, when I needed constants for printer codes (bold on, bold off, etc.), while browsing through the Epson manual, I defined some constants which I don't currently use, but which I might use later.

I get this point, but that applies to .h files I create for my own use. I don't get why VFP put's a definition in an .h file that's only used once. I'm never going to see it if I don't study the code. I would understand if it was replacing some meaningless value (like #DEFINE MB_OK 0 && OK button only), but [#DEFINE APP_MACRO_RESTORE_LOC "Restore"] doesn't make any sense to me if it's only used once. Although I do understand the localization argument. Don't agree that it's the best way to go, but understand it.