Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Xlsx to xls
Message
From
03/04/2014 12:56:14
Mike Yearwood
Toronto, Ontario, Canada
 
 
To
03/04/2014 11:00:59
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Germany
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows Server 2012
Network:
Windows 2008 Server
Database:
MS SQL Server
Application:
Web
Miscellaneous
Thread ID:
01597868
Message ID:
01597998
Views:
39
>:)
>You right with calling
>
>FUNCTION or PROCEDURE and PROGRAMS
>If you use SET PPROCEDURE TO you can call a prg just as function or procedure.
>
>
>
>>In VFP, it's not how it's declared. It's how it's called. You can name something FUNCTION or PROCEDURE. Makes no difference.
>>
>>>Now you must declare that FUNCTION and PROCEDURE is the same in VFP. Or do you see any diffence, except declaration?

I find it wasteful to write the declaration at all. Make every function or procedure a separate .PRG file. You can still call it as a function or procedure. It will run without an additional SET PROCEDURE command elsewhere in the app. Further, just add it to the pjx and it will be run in the exe again without any additional set procedure command. I believe it's the fastest way for fox to execute code.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform