Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
SFErrors.h
Message
From
11/08/2002 11:01:18
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivia
 
 
To
10/08/2002 18:22:52
General information
Forum:
Visual FoxPro
Category:
Stonefield
Title:
Miscellaneous
Thread ID:
00688364
Message ID:
00688411
Views:
21
>Thanks for your response.
>
>I didn't make my question clear. I'm not really good with "include" files.
>
>The variable that is not being found (cnErr_CANNOT_FIND_DLL_ENTRY) is defined in the include file SFErrors.h. Nowhere up the calling chain of programs does the cstr "sferrors" appear. I'm assuming that it should appear someplace up the calling chain in an include statement, like so: "#include SFErrors.h".
>
>Is this not correct?
>
>Thanks,
>Dick

In principle, yes, but please note that it can also be called indirectly. For instance, I have several include files - and might want to add an additional include file at any moment.

To ease maintenance, I have a global include file - let's call it MainInclude.h - with contents similar to the following:
#include PrinterConstants.h
#include UserTexts.h
#include SFErrors.h
...
All my other files now include a single include statement:
#include MainInclude.h
Now, I can add an additional include file (or delete it) in one single place - namely, in MainInclude.h.

Also, in forms and classes, include files are specified with the menu command "Form | Include" or "Class | Include" - no code you can see in the code editor.

HTH, Hilmar.
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)
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform