Jan 26, 2013 at 9:49 PM
Edited Jan 27, 2013 at 1:32 PM
Maybe this is an obvious observation, but it wasn't to me a couple days ago.
I was loading PRGs onto AVFP on the web and spending time debugging directly in AVFP, but I found that simply debugging in VFP was faster and more efficient.
In the code below, I basically create some custom objects that I can uncomment when I need to test. In that way, I don't need to concern myself with the odd -- to VFP -- way of oProp calls in AVFP. I simply created a dummy custom Object
and properties for testing.
Seems like the PRG files take some time to clear in the on-line buffer. My experience is you can't copy PRGs right away to the web server. So if I have a pagnav.prg to update, I simply rename it pagnav1.prg and upload that without getting
a "file is in process" message. ( NOTE: See reply below which solves this issue. )
* pagenav.prg - Page Navigator code
* Test Settings to Use when you are debugging directly in VFP -- Simply comment and uncomment them as needed.
* Also you will need to uncomment and comment the LPARAMETERS line accordingly.
* Comment these out in production mode.
*!* lnRowsPerPage = 10 && Rows per page
*!* lnPagesToShow = 5 && Pages to display on the Pagenav widget
*!* lnCurrentPage = 2 && Current page number
*!* lcDirection = "Next" && Vale of button -- Next, Prev, First, Last
*!* lnRecordCount = 100 && Total records in the cursor
*!* oProp = NewOBJECT("Custom")
*!* oProp.ScriptPath ="Scriptpath"
*!* oProp.Action = "Action"
*!* oProp.SessID = "SessID"