Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Loosing path on using 'Set Procedure To'
Message
From
12/10/2004 00:09:19
 
 
To
10/10/2004 23:05:53
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00950315
Message ID:
00950596
Views:
13
The path is quite short and the latter ones get added correctly. It is something to do with the actual name but have not yet found out exactly what. Renaming the file eliminates the problem but doesnt explain why.

Regards
geoff Scott

>>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.
>
>A couple of SWAGs:
>
>- Does it still happen if you do something like
SET PROCEDURE TO (eSTDDIR+'stdfunctions.prg') ADDITIVE
- I don't know if there's a limit on the total length of SET("PROCEDURE") but is it possible you're exceeding say, 255 characters?
May all your weeds be wildflowers
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform