Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Loosing path on using 'Set Procedure To'
Message
From
12/10/2004 03:38:05
Neil Mc Donald
Cencom Systems P/L
The Sun, Australia
 
 
To
10/10/2004 22:28:14
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00950315
Message ID:
00950615
Views:
10
Hi,
Try swapping the order of the SET's i.e.
#define eSTDDIR '\Std\'

SET PROCEDURE TO 'MyApplication.prg'
SET PROCEDURE TO eSTDDIR+'registry.prg' ADDITIVE
SET PROCEDURE TO eSTDDIR+'sl_que.prg' ADDITIVE
SET PROCEDURE TO eSTDDIR+'std.prg' ADDITIVE
SET PROCEDURE TO eSTDDIR+'stdfunctions.prg' ADDITIVE
If the system uses something like LOCATE to find the PROCEDURES, a call to std.prg would find stdfunctions.prg first.
That probably why changing the name worked.

>Hi
>
>I have a weird problem whereby I loose access to functions in a procedure program.
>
>
>#define eSTDDIR '\Std\'
>
>SET PROCEDURE TO 'MyApplication.prg'
>SET PROCEDURE TO eSTDDIR+'stdfunctions.prg' ADDITIVE
>SET PROCEDURE TO eSTDDIR+'std.prg' ADDITIVE
>SET PROCEDURE TO eSTDDIR+'registry.prg' ADDITIVE
>SET PROCEDURE TO sl_que.prg ADDITIVE
>
>
>The weird thing is that it only happens on the "stdfunctions.prg" and never on the first time I run my program in the development environment. When I do a ?SET("Procedure") I see that this program has lost its path yet the others have the path.
>
>Also, rebuilding my project also stops it happening the next time I run it.
>
>Any ideas what is happening?
>
>Regards
>Geoff Scott
Regards N Mc Donald
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform