>Ok... I'm using "set procedure to" and that works fine. I'm investigating using a global
>object with methods for my procedures as suggested by another user. One last question
>on this thread though... Is there any way to have global constants "#define...." so that
>I don't have to include the .h file in each and every form I need it? Maybe properties of
>a global object would work?
>

In development, the _INCLUDE variable in VFP6

---

_INCLUDE System Variable

Specifies a default header file included with user-defined classes, forms, or form sets.

Syntax

_INCLUDE = HeaderFileName

Arguments

HeaderFileName

Specifies a default header file of predefined compile-time constants automatically included with user-defined classes, forms, or form sets. If your header file is in a directory other than the current default directory, include a path with the header file name. Contains the empty string by default.

Remarks

You can also specify the default header file with the Default Include File item in the File Locations tab of the Options dialog box.


>>Joe,
>>
>>You can use SET PROCEDURE TO .... ADDITIVE
>>
>>Although I gave up FPW style monolithic procedure files a long time ago. I find individual .PRGs much easier to use and like the finer granularity they provide.
>>
>>>So there is no way to have a bunch of procedures in a file that you can
>>>call globally? I have to have a separate file for each procedure I want to call?