Hi Thierry,
As I mentioned last week, I'll post here so as to help educate ProFox on the product, using the [FIC] subject prefix.
When I ran the latest adaptation assistant, I made the C:\TEST folder (and subfolders) all read-write to remove the readonly errors I had prior. As per instructions at the end of the FAA, it says to run it and make sure it still works. I took that to mean I should run the newly built EXE. So I did: DO c:\test\dev\somerset\mbss_reports.exe
*-FIC- Replaced by FoxInCloud Adaptation Assistant version 2.24 (copy mode) on 06/28/2017 06:24 AM *-FIC- WAIT WINDOW TIMEOUT 1 lcSalutation + lcUser
wWAIT(lcSalutation + lcUser, 'WINDOW TIMEOUT 1')
It errors on the FAA-generated wWAIT function with which FAA replaced my WAIT WINDOW TIMEOUT (also seen in the commented out code above).
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???
Thanks, --Mike
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 ---
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]
As much as I love Profox, I'd definitely move the discussion over to the FiC forum on the Westwind message boards.
https://support.west-wind.com/
West Wind Message Boardhttps://support.west-wind.com/ support.west-wind.com Support Web site for West Wind tools and products and general Web and Enterprise development discussions for Visual FoxPro and .NET developers.
________________________________ From: ProfoxTech profoxtech-bounces@leafe.com on behalf of mbsoftwaresolutions@mbsoftwaresolutions.com mbsoftwaresolutions@mbsoftwaresolutions.com Sent: Saturday, July 22, 2017 1:23:26 AM To: profoxtech@leafe.com Subject: Re: [FIC] Problems with Adapted code
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]
On 2017-07-22 09:04, Richard Kaye wrote:
As much as I love Profox, I'd definitely move the discussion over to the FiC forum on the Westwind message boards.
https://support.west-wind.com/
West Wind Message Boardhttps://support.west-wind.com/ support.west-wind.com Support Web site for West Wind tools and products and general Web and Enterprise development discussions for Visual FoxPro and .NET developers.
The idea was to help increase FIC awareness here though, hence the [FIC] prefix. https://leafe.com/archives/msg/508074
Part of me wants to just go over to the other forum for hopefully a quicker response (from other FIC dudes already), but the effort here was to help ProFox become more familiar with Thierry's FIC software.
After running Step 2 in FAA, I reviewed the changes it said I had to
make. Made nearly all of them.
Be aware that, as you're running in test mode, FAA can override your changes at any time by re-copying the file into the test\ folder
I will say that when reviewing the file in FAA, it makes the file
ReadOnly
This is to prevent from adapting code in test mode, for the above reason…
when I close that preview screen, the file remains ReadOnly
reason why we've removed this feature until we find a proper event to remove the 'read-only' flag
errors on test and prod compiles
normal - building the 'test' and 'prod' projects always fail to find references that are included in aw.app; FAA warns about this
final crash (https://www.screencast.com/t/Jb3nIbUld)
This error probably happens at server startup, when instantiating the 'xxxSets' class of xxxSets.prg
xxxSets.prg holds the app init code from your desktop app that FAA has 'tried' to recycle; you need to review this code as FAA does not always do a perfect job identifying code that can run in Web mode or should remain in desktop mode only.
xxxSets of xxxSets.prg is intended to be the app's init class shared by desktop and web instances; see http://foxincloud.com/tutotest/fileDisplay.tuto?tutoLAN.prg and http://foxincloud.com/tutotest/fileDisplay.tuto?tutoSets.prg
Thierry Nivelet FoxInCloud Give your VFP app a second life in the cloud http://foxincloud.com/
Le 22/07/2017 à 07:23, mbsoftwaresolutions@mbsoftwaresolutions.com a écrit :
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]
again, adapting code in test mode is probably not a good idea
test mode is only intended to make sure that, after automated adaptions, desktop application still works the same as usual.
real adaptations should always be done in source mode
we've emphasized this point in the notice by clicking on blue question mark near source/test selection
Thierry Nivelet FoxInCloud Give your VFP app a second life in the cloud http://foxincloud.com/
Le 24/07/2017 à 11:08, Thierry Nivelet a écrit :
After running Step 2 in FAA, I reviewed the changes it said I had to
make. Made nearly all of them.
Be aware that, as you're running in test mode, FAA can override your changes at any time by re-copying the file into the test\ folder
I will say that when reviewing the file in FAA, it makes the file
ReadOnly
This is to prevent from adapting code in test mode, for the above reason…
when I close that preview screen, the file remains ReadOnly
reason why we've removed this feature until we find a proper event to remove the 'read-only' flag
errors on test and prod compiles
normal - building the 'test' and 'prod' projects always fail to find references that are included in aw.app; FAA warns about this
final crash (https://www.screencast.com/t/Jb3nIbUld)
This error probably happens at server startup, when instantiating the 'xxxSets' class of xxxSets.prg
xxxSets.prg holds the app init code from your desktop app that FAA has 'tried' to recycle; you need to review this code as FAA does not always do a perfect job identifying code that can run in Web mode or should remain in desktop mode only.
xxxSets of xxxSets.prg is intended to be the app's init class shared by desktop and web instances; see http://foxincloud.com/tutotest/fileDisplay.tuto?tutoLAN.prg and http://foxincloud.com/tutotest/fileDisplay.tuto?tutoSets.prg
Thierry Nivelet FoxInCloud Give your VFP app a second life in the cloud http://foxincloud.com/
Le 22/07/2017 à 07:23, mbsoftwaresolutions@mbsoftwaresolutions.com a écrit :
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]
Mike,
another point: if you don't mind, make sure to follow up on the hint and solutions we provide here and/or by PM: it helps us sort out what is pending or not, and what needs more work.
Thanks,
Thierry Nivelet FoxInCloud Give your VFP app a second life in the cloud http://foxincloud.com/
Le 22/07/2017 à 07:23, mbsoftwaresolutions@mbsoftwaresolutions.com a écrit :
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]
Should I use the WWWC forum instead?
On 2017-07-24 06:27, Thierry Nivelet wrote:
Mike,
another point: if you don't mind, make sure to follow up on the hint and solutions we provide here and/or by PM: it helps us sort out what is pending or not, and what needs more work.
Thanks,
Thierry Nivelet FoxInCloud Give your VFP app a second life in the cloud http://foxincloud.com/
Le 22/07/2017 à 07:23, mbsoftwaresolutions@mbsoftwaresolutions.com a écrit :
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
-
Jean MAURICE -
mbsoftwaresolutions＠mbsoftwaresolutions.com -
Richard Kaye -
Thierry Nivelet