>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.
Yes, I assume it was done for localization, as explained by others.
Walter Meester also explained the alternative of reading from a DBF file.
Another localization alternative I have tried is to read values from a text-file, and store them in public variables. See download #
10009 (the backup program reads options from a text-file).
Personally, I like the text-file because it can be edited by the end-user without special software.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
