Hi Thierry,
Finally getting back to this.
After running Step 2 in FAA, I reviewed the changes it said I had to make. Made nearly all of them. (Some didn't seem applicable...for example, no need to flag my pathing in my variable declarations MyVar as MyClass of c:\dev\client\classes\mjbbase.vcx). I made these changes in my newly auto-created C:\TEST\dev\client... folders (instead of C:\DEV\CLIENT... folders). I will say that when reviewing the file in FAA, it makes the file ReadOnly and then when I close that preview screen, the file remains ReadOnly and I have to use Windows Explorer to change the file attribute back to R/W. (Also, it only made the VCX part of the classlib R/O...not the VCT also). It'd be nice if it didn't change the file to R/O since it's the auto-created C:\TEST... copy anyway.
Got errors on test and prod compiles, but it still powered through and said completed, green light, ready to go. Verified Fox logo showed in the browser. Ok. Then choose a form to launch, but then it crashed.
Screenshots: - prod (https://www.screencast.com/t/BEvNWqJjkD) - test (https://www.screencast.com/t/JSQUSsAkVU4t) - final crash (https://www.screencast.com/t/Jb3nIbUld)
Met another potential client today whom could benefit greatly from this, so I'm hoping your team can advise me on how to fix this! Would it help to publish my trials on the WWWC site instead? Maybe it's more FIC traffic there?
Please advise...thanks! --Mike
On 2017-07-05 12:37, Thierry Nivelet wrote:
Hi Mike,
1- yes, FAA replaces all WAIT by wWait() - you can let FAA do this replacement Reviewing the adaptations in the FAA grid (and the explanations below) will probably help you understand what FAA does and why.
2- provide the error you get so that we can find a fix. To get help, « I have an error » or « it does not work » always require additional detailed info. to help sort the issue out.
3- « FAA completes »: which FAA step do you mean? 1, 2 or 3? If you’ve completed step 3 successfully, you need to (xxx being the app prefix you chose during steps 2 and 3): in VFP IDE: do <path to>\xxxTest.prg in browser: localhost/xxxTest
Kind regards,
Thierry Nivelet FoxinCloud Give your VFP app a new life in the cloud http://foxincloud.com/
Le 5 juil. 2017 à 08:13, mbsoftwaresolutions@mbsoftwaresolutions.com a écrit :
Question #1: do WAIT WINDOW instructions need to be taken out of the original code base?
Question #2: what's my next step?
Question #3: after FAA completes, how do I launch this newly adapted app in my local browser???
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]