Hi!

I have no idea. #DEFINE constants looks very weird in VFP. We had a lot of troubles with them in VFP5 until we figured out all problems and worked around them by using some sort of framework.

>>Hi!
>>
>>Because #INCLUDE affects the module it compiles and al following modules in the compilation process. This means that when your form(s) compiled before main program, they will not see constants, because they defined only in the main program. Note that you cannot define order of compilation. However, it is not needed. You can include file into each form or class using 'Include file...' menu item for form or class. However, if you hav a generic global include file(s), use _INCLUDE system variable. See help for it. You can put all your include files into main.h include file using the same #INCLUDE directive (VFP allows INCLUDE of INCLUDE ;), than specify main.h in _INCLUDE system variable.
>>
>>>When I put an #INCLUDE statement in my MAIN program, I can't use any of the constants in forms etc.
>>>
>>>Why is this?
>>>
>>>Thanks
>>>Kev
>
>Vlad,
>
>Question for you...
>Why can't we put the #Include in the forms's baseClass so this could be another inherited property?
>I haven't tried this for a long time but from what I remember I had to put it into each individual form.