Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Compiler Directive... _VFP not allowed?
Message
From
08/07/2003 18:42:01
 
 
To
08/07/2003 16:01:14
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00808212
Message ID:
00808263
Views:
15
This message has been marked as a message which has helped to the initial question of the thread.
Joe,

Not only is _VFP not allowed, but it appears you cannot use any variable at all, even a public variable, or a property of _SCREEN. Further, you can use internal VFP functions in the expression, but you cannot use a user defined function.


>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