Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Procedure Commands
Message
From
23/03/2004 15:26:44
 
 
To
23/03/2004 15:15:47
Chad Ashpole
Ads Information Systems, Inc.
Minneapolis, Minnesota, United States
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00888970
Message ID:
00889014
Views:
18
Yes, that's what I am saying, DO SOMETHING will not return anything, SOMETHING() will return something.

>I understand what you're saying and I wish it were that easy. However, I'm trying to avoid swapping proc files around. That is why I was using DO myProc WITH param1 IN ProcName so I wouldn't have to issue SET PROCEDURE and RELEASE PROCEDURE calls. Unforeturnately the proc I am calling using DO PROCEDURE is part of a compiled program and I can't change its code. It just issues RETURN .T. or RETURN .F. It sounds like you're telling me I can't use DO PROCEUDRE and determine what value the proc returns. The only way is to issue a SET PROC TO ProcName then val = x(param1).
Previous
Reply
Map
View

Click here to load this message in the networking platform