Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Compiler Directive... _VFP not allowed?
Message
From
09/07/2003 10:36:59
 
 
To
09/07/2003 01:37:16
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Germany
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00808212
Message ID:
00808491
Views:
12
Agnes,

Unfortunately, that won't work...the precompiler directive does not even see public variables.

I had already tried to do this in beforeBuild() method of projecthook.

>
>Update:
>Just an untested idea. Use a project hook to put the information into a public variable.
>Use this var instead of.
>
>Possibly to put the complete reference into a var like
>
>*inside the hook:
>PUBLIC;
> poActiveObject
>
>poActiveObject = _VFP.ActiveProject
>*compile
>RELEASE;
> poActiveObject
>
>
>Agnes
>>Hey all,
>>
>>Can anyone tell me what is wrong with the following compiler directive:
>>
>>#IF (OCCURS('VISMM.PJX', UPPER(_VFP.ActiveProject.Name)) > 0)
>>
>>This was going to be such a sweet way of conditionally compiling code depending on the name of the project. I am sure I can think of other ways, but this seemed the most elegant. But I get the error: "Preprocessor expression is invalid." when compiling this for the above line.
>>
>>OCCURS is OK, but when I try to use the _VFP.ActiveProject.Name it seems to get cranky. Can anyone tell me if this is a limitation I should be aware of? The expression:
>>
>>(OCCURS('VISMM.PJX', UPPER(_VFP.ActiveProject.Name)) > 0)
>>
>>evaluates just fine to .T. or .F. in the command window...
>>
>>I would appreciate any help, and thanks in advance!
>>
>>Thanks,
>>JoeK
Steve Gibson
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform