Returning to Beta 4 the problem does not occur. Remembering that I use a way to customize the html and javascript as the photo below.

Hi Arcadio,

Can't say why this happens by just reading code…
Can you reproduce in dev. & debug mode, and provide the full call stack when error occurs?

Ok! The error occurs when the form is loaded with the formmaster. What can I send to you? A video? Maybe explaining to me what you changed in this beta 5 will also understand why it is not working now.

I need that you reproduce the error in dev and debug mode (do atPJcompileDebugMode), and provide debugging info when the error occurs

The error happens the first time I call the form. Then it stops happening.

I understand the error and where it happens, I just can't understand why it occurs.

if you run using DEBUGMODE, does execution stop when error occurs?

I will try here, the change you made has no way to parameterize, to have the previous behavior?

In DEBUGMODE the problem does not occur.

It is something in the site and temp folder. I don't understand much about this process. If I enter the screen once the second time, there is no more error show.

In DEBUGMODE the problem does not occur.

Thanks for trying, we'll try to reproduce on our side.

What does your form look like?

Foxincloud's logo appears, there when I ask to see the code of the page this way, it appears as in the first photo of this topic.

Can you please share a screenshot of the form where error occurs?

Hi Arcadio,

Could not reproduce with #200 forms of various origins…

I confirm that, when compiled with DEBUGMODE = .T. and starting server in the VFP IDE, execution should stop when the error occurs:

modify project xxxTest nowait
do atPJcompileDebugmode with .T.
do xxxTest with 'form_on_error.scx'

Okay, I'll try. Debugmode does not occur, it is an intermittent error, which disappears on the second call of the form. Follow below 2 videos.

https://youtu.be/GcDC2VlNcmw

https://youtu.be/0lfqh9kxEdg

Still not sure why your issue occurs, however this should be a workaround:

modify command awHTML.prg

&& replace

if m.llForm
  this.getHTML_frm_Script_tabCycle

&& by

if m.llForm and m.this.lTabIndex && 2020-10-02 thn -- {FiC V 2.31.0-beta.6} {en} moved up https://support.west-wind.com/Thread5VI0W7AGY.wwt
  this.getHTML_frm_Script_tabCycle

It worked! I had no more error messages. Thank you!

great, thanks for the feedback!

Taking advantage of this problem that I had, wouldn't it be interesting when crash is occur in formmaster, show the error without having to enter the source code of the page?

this feature is in the roadmap

Hi,

This problem occurred again in beta 7. Do I have to make the change manually in every new version?

Hello Arcadio,

If you change FoxinCloud source code for this issue, can you share your changes?

modify command awHTML.prg

&& replace

if m.llForm
  this.getHTML_frm_Script_tabCycle

&& by

if m.llForm and m.this.lTabIndex && 2020-10-02 thn -- {FiC V 2.31.0-beta.6} {en} moved up https://support.west-wind.com/Thread5VI0W7AGY.wwt
  this.getHTML_frm_Script_tabCycle

If I put this code above, the problem does not occur, I thought it would be fixed in the foxincloud code.

I thought it would be fixed in the foxincloud code

It was, and unfortunately the change was lost during a sync between dev. machines.

Please report ASAP when you see this happen. Thanks

I think it would be u just to make the change again, right? I didn't understand what you want me to do.

Please tell us ASAP about changes missing in a new release

Got it! I only noticed this for now. Don't you use a source control like team foudation?

We do, and sometimes have sync failures

If I put this code above, the problem does not occur, I thought it would be fixed in the foxincloud code.

fixed, please double check in the next release scheduled end of January

OK! Thank you!