Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Will it present any problems?
Message
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 9
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01075367
Message ID:
01075390
Views:
13
>I see. In other words every time we open the SP with modify procedure command the SP is getting compiled behind the scene and all the constants are getting included inside the compiled code, right?
>
>>It's compile time directive not a command.
>>
>>>At the top of the Stored procedure in our database we have #INCLUDE '\MMORTALS\COMMON30\INCLUDE\FRAMEWRK.H' In production we don't have the same directory structure as we have in development. The framework.h is included in the project. Do you see any problems using it this way?
>>>

Yes and no. Everytime you opened SP for editing and after that you compile it (no meter you do that manualy or in Backgroud) Compiler not include the constants it just search and replace them in your code. i.e.
#define CRLF CHR(13)+CHR(10)
Messagebox("First Line"+CRLF+"Second Line")
compiler search where you use CRLF and replace the and then compile, so it compiles code like this:
Messagebox("First Line"+CHR(13)+CHR(10)+"Second Line")
not like this:
m.CRLF = CHR(13)+CHR(10)
Messagebox("First Line"+CRLF+"Second Line")
I hope I explained this understandable :o)
Against Stupidity the Gods themselves Contend in Vain - Johann Christoph Friedrich von Schiller
The only thing normal about database guys is their tables.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform