After it's run the VFP function, which could write out to a text file on the server or to a VFP table, I could then employ VFP to read the data from the next web page.
Sent by Art Bergquist on 09/09/2019 11:34:58 AM:
Thanks; the use case was to store information via VFP into a text file for another web page to use; the web page I'm POST-ing to is very similar to the upper section of your Examples\Download.FWx. As a result, it doesn't have HTML like you have in the lower section of Examples\Download.FWx.
Between the time I sent my question below and the time you had responded, I had switched to employing hidden <input>s to store 4 pieces of information the next page uses [I can easily read the hidden <input>s from the next page via Request.Form() calls].
Have you any insights WRT how I could read an HTML5 data- attribute set in the previous web page in the above scenario I described?
Sent by FoxWeb Support on 09/03/2019 01:12:02 PM:
At the same time, I don't understand why you want to call a FoxWeb script through OnClick, instead of simply specifying it in the href attribute. Why not call the script directly? Is it because you are trying to display content from a different page, once the script is done? If yes, you can redirect the user to the other page through the content returned to the browser by the script.
FoxWeb Support Team
Sent by Art Bergquist on 08/31/2019 05:04:47 PM:
|onclick="<%= RecordDocument() %>"
RecordDocument.Prg contains the following code:
|STRTOFILE('Test message', 'RecordDocument.Txt', .F.)
The problem is that when I click on an anchor that has its onclick defined as above, it doesn't appear to run RecordDocument.Prg (since RecordDocument.Txt doesn't get created).
I've also tried not including the equals sign, as follows:
onclick="<% RecordDocument() %>"
but that didn't work (and I don't believe that's the correct syntax anyway).
Has anyone ever tried doing something like this?