Did you read this answer ?
http://www.west-wind.com/wwThreads/Message3F2047O24.wwt
It should answer your question about identification ...
HTH,
ThN
Thierry,
PROCEDURE Form1 is within xxxProcess class.
"http://localhost/sa/bin/wc.dll?FoxInCloud~Form1"
Form1 is instantiated and html generated. Then this error appears in VFP IDE:
Sa1process.wform() Awajax.forminitsave() - Access to form 'form1_scx' requires a prior identification.
As previously written, if
PROCEDURE Form1
is within xxxProcess class, it's correct
FoxinCloud matches Foxincloud", yes - no?
yes, case insensitve
Obviously top form should be modeless; modal forms are used to return a user's choice (like a messageBox)
You don't need to build an exe to test - you can run xxxTest from within the VFP IDE like any wConnect application.
At this point you only need ONE exe: xxxTest.exe - xxx.exe is not used - later on you'll build xxxProd.exe to produce your production server.
Hope this will anwser your questions and help you move forward.
thn
Thierry,
our Form1 is still not launching. We have no main program and no READ EVENTS. awserver has a READ EVENTS. Our sa.server.prg has the following code:
PROCEDURE Form1 && http://localhost/sa/Form1.sa * or http://localhost/sa/bin/wc.dll?FoxInCloud~Form1
RETURN this.wFormStandardPage('Form1.scx')
This seems to match what you are recomemending, yes - no ?? "FoxinCloud matches Foxincloud", yes - no?
We changed Form1 back to modeless window type. May a top form be set to either modal or modeless, or must the top form always be modal. Each time we make a change we re-run FAA and rebuild the sa1.exe. We also create sa1test.exe. When we create an executable, we get "Access to system registry denied". we do not know how to fix this.
if you look at xxxServer.prg with VFP document view tool, you'll see 2 classes: xxxServer and xxxProcess.
xxxProcess is what wConnect uses to process requests: parameter in after "Foxincloud~" in "http://localhost/sa/bin/wc.dll?Foxincloud~form1" should match the name of a method of the xxxProcess class (this is wConnect default naming pattern).
If you use a script mapped extension such as ".sa", mapped to http://localhost/sa/bin/wc.dll?Foxincloud, then method name becomes URL 'stem': http://localhost/sa/form1.sa
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