Little hard to suggest much without seeing the script you created.
- You can upload a screen shot of your script by clicking the edit link to your original message and uploading it there
- You can upload a screen shot to a file share site and post the download link to a new response you post here.
- You can print a script to a PDF, open the PDF and then select and copy the script as text from the opened PDF.
- If You have FileMaker advanced, you can generate a database design report and copy the script as text from there.
I'm still not sure what was causing it but I have determined that it wasn't the script. It also happened whenever I exited a field. I also checked to make sure that the field wasn't triggering the script without me knowing it.
If you have FileMaker advanced, you can try testing your file while the script debugger is enabled to see if any script triggers are being tripped. (And scripts can trip script triggers just like the user can when they change layouts, records, enter/exit fields etc.)
Interesting, this is happening to me too. If I run it under the debugger, it works fine. But if I just run the script, the Scroll Window script step just doesn't do anything. Very strange and might be a bug.