I can't seem to get this script step to go to the next portal row. I can get it to go to the last or first but not next. Has anyone ever seen this?

It would help to see the rest of the script that's giving you trouble.

I just tried creating a new layout with a new portal with just three fields from the original layout I was using. I did a got to first, then a loop, then a pause, then a go to next, exit after last.

It does the same thing. Selects the first row, then pauses. Hitting continue causes it to blink and reselect the next row.

I tried this exact procedure with 2 fresh new files and it worked.

What I did figure out is that its another script running in the loop that is causing this. If I take it out of the script, it works fine. Unfortunately, that script is the whole point of running this script. So if anyone has any insight as to why another script running would cause this script to error out, I'm all ears. Thanks!

Edited January 31, 200620 yr by Guest

When asking for free advice provide enough information so we don't have to play guessing games. Post your script.

I just had a hard time with scripts of this type. What I eventually had to do was store the portal row number as a global and then go to the next row that way with a calc. I suspect you are having the same problem. Post the file sans data and maybe I can help.

John

I agree with Ender and Bruce--there's not enough information here. But, HEY, that's never stopped me before!

I suspect that your script loop goes to the portal row, and then follows with a command that takes FM out of the portal (even momentarily), which resets the portal position.

Johnnyboy's solution, while not providing an explanation of this, is nonetheless the solution I have heard (and used) as well.

HTH,

David

So if something is to be done with a portal content of records, why isn't it done in the related records instead, after a record have been processed could an omit record get rid of the present record, shifting the stack upwards, making the cursor jump right into the record which used to be the second one, this is done under loop control, which is terminated when the found set (via GTRR(SO)) is empty.

Woking form primary records portal is slow compared wit this.

--sd