Skip to main content

Running Dynamic Code with ExecScript

The Wiki has an interesting post on how to run dynamic code. While much of the post deals with using BINDEVENT, I just want to make a note on ExecScript.

This is one of the best additions to Visual FoxPro. In one application, we used to offer the ability for users to write their own validation rules (provided they knew how to write FoxPro expressions). Now, we take it even further: they can write their own full scripts.

Not only that - but we offer popular rule "templates" that users can build their existing rules from and use TEXTMERGE to fill in the appropriate values.

How so?

A rule table with a field for
Rule Description (cdesc)
Rule Script (mrule)
Rule Parameter (cparm)

The code that executes the rule does a

EXECSCRIPT(TEXTMERGE(mrule,"*PARM*",cParm))

The user only needs to fill in the Rule Description and the parameter - everything else is hidden from them.

Our templates start with easy to use templates like : This field must be filled in or here is a valid list of values to "Don't allow this entry unless today's date is Dec 31 and the user's name is XXXX".

By using rule templates, more advanced support staff can write rules that others then simply re-use by filling in the templates.

Previously, we had a bunch of FXP files lying around in folders where people had to learn the expression and the parameters. With ExecScript, you can put all of these into a library of functions and call them with Friendly names.

"Oh you need to send an email to a user?" Instead of making them learn how to write SENDEMAIL.PRG, they can call a function library call like

CallFunction("Send Email", "person@company.com", "Hi")

This is almost like going back to macros in Excel and Lotus days, but it becomes infinitely easier on the end user.

If you've never used ExecScript, try it out.

It's been in Visual FoxPro since VFP 7.

Comments

Popular posts from this blog

Attending Southwest Fox 2019 could change your life - Find out how

Southwest Fox is coming up in October and as I do every year, I spoke with the organizers Rick , Doug and Tamar on the FoxShow. Deadlines for Southwest Fox: Super-saver price (before July 1): $695 Early-bird price (before August 1): $770 Regular price (August 1 and later): $820 This year, I took a different approach with separate shows for each organizer but the main message is still the same : July 1st is their Go/No-Go date. Conferences don't talk about this very often. I don't think developers really question if Apple will hold their WWDC in June or Microsoft will hold their Build conference - but that's because those conferences are vendor-led. Southwest Fox is a community-driven conference - it's not driven by a company with an agenda. Listen to the interviews and you can hear how important each of the organizers feel the live connection between speakers and among attendees.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub . A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article  : "...   people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack? Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site: http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older. Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments. But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward. FoxPro VFP