My personal peeve on it is I can't pull just a section out for testing. We've got a couple of VFP apps that were outsourced (doncha just HATE that word?) and the original programmer had #DEFINES out the yingyang. He even defined .t. = TRUE.

ok...maybe that's a little nit-picky, but the biggest problem trying to do anything with this code is that he was also a function junky. So, if ya wanna chase down what's going on, first you start with the variable (ln_NumberofReportInstance, for example) - that goes to the first function where it gets stuffed into ReportInstanceCount which then gets passed to yet another procedure where it becomes RptInstNum and is compared to MaxInstanceCount - which is in the include file and is defined to be 1. (and that is a real example, and one of the shortest chains)


>Hey all.
>
>Maybe this is rhetorical.
>
>But why do almost all VFP code examples insist on using a #DEFINE variable for MESSAGEBOXs? For example,
>
>=MESSAGEBOX("You screwed up!",MB_ICONSTOP,"Error!")
>
>Seems to me this is counterproductive. Why not just use the doggone number 16? Otherwise, you have to remember to do the #DEFINE or attach the .H file.