12:37:05 AM
3F701BPYC
In your case, you probably renamed the "xxxProcess" class as "sa1Process". We use the name "xxxProcess" to let anyone use our answers regardless of their specific project prefix.
FoxInCloud always treated a form called by xxxProcess.wForm*() as modeless.
Answer to your question #2 is here : http://www.west-wind.com/wwThreads/Message3F2047O24.wwt;
please consider using the 'search' functionality of this message board as much as possible.
HTH,
ThN
Thierry,
We did not find a xxxProcess class. We found PROCEDURE SampleForm in xxxServer.prg. We added PROCEDURE Form to our sa1server.prg.
Form1 is succesfully launched but then closes, perhaps because Form1 is modelelss (?). We changed Form 1 to modal and now we are getting an new error message sa1process.wform() - awajax.forminitsave access to form1 requires a prior identification.
are we close?
Hi Troy, Garth,
Have your added a PROCEDURE Form1 to your xxxProcess class?
You should find some commented sample code there.
HTH,
thN
Hi Thierry,
At the request of our clients, we are in the process of developing a more detailed how-to guide on developing FiC Apps.
We have created a 2-form sample VFP app to use with our guide. We have gone through all the FiC how-to guide steps.
Our VFP app is in a directory called FiCTest. Our project is called SA1Test. We replaced XXX with SA1. The adapted code in the same directory the VFP app is in. The FAA app code is SA (FAA does not take SA1). Our IIS virtual directory is called SA. Form1.init contains the pathing: SET PATH TO "programs,forms,reports,images,data" ADDITIVE. this same path is in sa1sets.prg.
We can get FIC to init through the browser using http://localhost/sa/bin/wc.dll?FoxInCloud~Default and get the FIC screen. But when we try to run form1 (the parent form) with http://localhost/sa/bin/wc.dll?Foxincloud~form1 we get Parameter Passed: Form1 Error: Unhandled Method.
Any help would be appreciated.
Troy Randle and Garth Groft