You can use the "@" syntax to call a procedure within a script (for details refer to the Locating and Addressing Scripts topic in the FoxWeb documentation), but why not split the procedure to a separate script?
Sent by P.F. McCracken on 03/08/2007 05:55:04 AM:
The program is efns.fwx. That is the entire script with sub routines.
That process had looked like this Response.Redirect("efns.fwx") . I now changed it to a Form submit process to try to send back the variables that are needed in the next process. I finally got it to go back to the program. But it strart from the beginning.
Do you have any ideas for referencing a sub-routine with in the script?
Sent by FoxWeb Support on 03/07/2007 02:05:01 PM:
Response.Redirect should be working fine. What's the URL that appears in your browser's location bar after the redirect from your ASP script? Does it look like a valid URL for calling your .fwx script? What does your call to Response.Redirect look like?
Sent by P.F. McCracken on 03/07/2007 10:08:15 AM:
1) I am sending form information out to an ASP page using ASPUpload for our very large file uploads of 200-250 Mbytes.
2) But I can not get it to return to the foxweb program and the location it was at. I tried a Response.Redirect, but it just acknowledges with a blank screen after completion. How do I return to the foxweb process?
Sent by FoxWeb Support on 03/07/2007 10:02:06 AM:
Please be more specific about the problem you are facing. I assume you know how to create links to fwx and asp pages and how to pass information in the query string, or via form variables. Is there a different problem?
Sent by P.F. McCracken on 03/07/2007 07:25:47 AM:
I am able to mostly send out to an ASP page
the variables I need. But getting it to
return to the FWX process routine that sent it
out is still a guessing game.
I need ideas & examples.