<p>
NEW INFORMATION:
</p>
<p>
I was successful with Safari on an iMAc. Cookies set to remove when browser closed.
</p>
<p>
I was unsuccessful with Chrome on iMac. Cookies set to <span style="font-family: Helvetica; font-size: 12px">Allow local data to be set (recommended)</span><span style="font-size: 10pt"> </span>
</p>
<p>
I was unsuccessful with FireFox on iMac. Cookies are set to Accept cookies from sites / Accept third-party from sites - Always.
</p>
<p>
Basically, the form loads well and submit is pressed after data entry. The problem is that nothing happens. The form stays loaded but does not respond.
</p>
<p>
The same thing happens when using Windows 10 except that I did not have Safari loaded.
</p>
<p>
Each browser used to perform correctly until recently. I suppose Windows 10 is not the problem but how old code is not working with 2 of 3 browsers now.
</p>
<p>
I will try scanning code to see what may be offensive as suggested.
</p>
<p>
</p>
<p>
Sent by Joe Goldsmiith on 01/12/2017 05:44:43 PM:
<p>
&nbsp;I suppose it had to happen sometime.
</p>
<p>
For years everything was working fine with any OS and browser. All of a sudden a few scripts created three years ago and never changed started to not work. Those with OS X of any version and any version of Windows from 8 on prior works fine. Windows 10 worked well until three weeks ago, or so, caused this script to fail. Perhaps it was due to a new update.&nbsp;<span style="font-size: 10pt">Issues fall into two categories.</span>
</p>
<p>
&nbsp;The first issue is&nbsp;Session.GetVar not receiving a&nbsp;Session.SetVar. Using response.write I can see it created at the parent script. On the child script the GetVar is blank using response.write. Until I noticed the issue it had updated all records in the same field due to the blank GetVar.
</p>
<p>
The second issue is in a form where the submit button shows pressed but nothing happens. It did not freeze, it just sat there even after a few submit clicks.
</p>
<p>
Every script still works with OS X and Windows 8 along with prior versions, it&rsquo;s just lately with Windows 10. Might anyone have also experienced this issue and perhaps found a fix?
</p>
</p>