Apr 11, 2015 at 5:33 PM
Edited Apr 11, 2015 at 5:34 PM
As I was studying the AVFP documentation, I ran into the names of objects such as oRequest, oSession, and oResponse.
I was wondering where these objects were created, but soon discovered that they don't need to be created because they are
to the language.
The AVFP objects and attributes are overlaid on top of Microsoft's ASP language. So studying the organization of the ASP language and examples of how it's used is educating me about AVFP.
A couple websites I recommend are:
The ASP Tutorial at w3Schools.com
-- includes lots of examples.
Active Server Pages on Wikipedia
Though I'm not sure how universally this applies, the objects are the same name except for the addition of "o" in the front, so:
oRequest.QueryString("action") in AVFP is: Request.QueryString("action") in ASP
oResponse.Redirect(lcNewPath) in AVFP is Response.Redirect URL
This knowledge should give comfort that AVFP is an actually built on the ASP industry standards. It's not an alien language. Things have been added to it to make it useful for VFP users.
In fact, if in the year 2150, the 32bit Windows goes away, we'll still have AVFP to run in the cloud -- or access using IIS on the desktop :- )
Lots of basis knowledge was cleared up for me when I visited the