I've had problems like this a couple of times where something that doesn't work under normal circumstances works just fine in Script Debugger. Try adding a very brief pause step to the script immediately after the script step that most likely takes the longest amount of time. You may need to move the pause step around to figure out where it will solve the problem.
I haven't found anything about this documented anywhere, but it appears that sometimes "slow" script steps essentially time out without an error, and the script moves on to the next step without the prior step having completed. Since everything is slowed down in Script Debugger mode, you never see the problem there. Inserting a pause at a strategic location in the script gives the "slow" script step a chance to fully complete before the script moves on.
Images can be slow to load. When you want to move past the 11 portal rows that are currently showing, it probably takes a while for FM to load up the new images. That should give you a clue where to insert the pause in your script.
Not sure why this is different in FM 13 vs FM 11, but maybe it has to do with differences in how the images are stored in FM 13? I assume you're using container fields for them and there were some changes to container management begininng with FM 12.
Potentially a simple fix, so it's worth a try, anyway!
Alex, can you post your script so we can take a look?
It's also just possible that the issue might be resolved by creating a new version of the portal. I suggest you try that and see if the problem persists.
I put in two .1 second pauses and got it to work. The portal flickers a bit but it works.
I am dissapointed that I keep having to create these workarounds to get Filemaker to do what I want it to do.
Is it too much to ask that in Version 13 I do not have to slow down a script so that it will work, especially as it worked fine in 11.
Thanks again Julie
I really do not want to create a new version of this portal as I have 15 or so portals on 5 different layouts very carefully layed out. I would have to pull the whole thing apart, and reconfigure all the triggered and conditional scripts. That is a tremondous amount of work.
Doesn't the conversion from fm7 to fmp12 automatically update the items (portals, containger fields etc..) to the latest iteration of them?
The images look better in Version 13 so I am hoping they act better.
Speaking of which can you direct me to a place where I can learn about the new functionality of container fields, and the other added features in 12 and 13. I would like to avoid buying a 700 page book for the 50 pages that I actually need to read.
Thanks again for your help.
I'm glad that worked.
The "timing out" of script steps is something I first encountered in FM 9 when an "Enter Find Mode" script step wasn't alway executing fast enough, and sometimes the "Set Field" commands that were meant for Find mode were happening in Browse mode -- eek! In that case I added a test for the correct mode, and that slowed things down enough so that solution has never had the same problem since, in 4+ years. Admittedly, that client's network is pretty slow which may have contributed to or caused the problem.
The other time I've seen it was a "Go to Layout" script step that didn't always happen fast enough, so the subsequent script commands were happening on the wrong layout. Inserting a brief pause solved that problem. In that case, the layout it was trying to go to was in an external database, which may be why it was slow. That was FM 12.
As I said originally, I've never seen this documented anywhere. I added the examples above in case someone in the future has a similar problem.
A slight correction. The free TechNet membership will allow access to support documents, this forum, etc. The paid subscription gives additional access to development licences etc.
And further to the main discussion, the new thumbnails feature in 12+ will probably speed up your script, alexander1z, as FM can be configured to create a thumbnail only to the size it needs for a given layout without altering the stored image at all.
My point about trying a new portal was to test whether this makes any difference. If it does, then it may indicate that the conversion of the portal during file conversion has left some bugginess in place. I appreciate that if this is a problem it could be significant, but it's worth checking for in my view, just in case. More likely, however, the problem could be resolved by updating container storage to take advantage of the new features.
I was able to open it.
Looks like scintillating reading.
I will have more questions, but it will take me awhile to get through it.