October 28, 200520 yr OK, this has been driving me a little nuts; I think I have uncovered a bug in FileMaker 7. I am working on a Time Tracking module, and several of my scripts use the Go to Portal Row script step. Some of my scripts use the steps in creating a new related record (by going to the last portal row), and some simply go to the first or last portal row and modify or clear a time. Sometimes, for no obvious reason, FileMaker fails to enter the portal, and inserting a Custom Dialog check after it should be on the correct portal row results in the Get(CurrentPortalRow) = 0. Has anyone else run into this? I can't think of anything I'm doing wrong; the file I'm working on HAS been converted from a FM 6 version, but if that's the cause, it's still a bug. :)
November 2, 200520 yr Matt-- Including your scripts would help... That said, does your script hierarchy include going to any other windows? If so, you have to remember to re-select the portal by using the Go To Portal Row script step again, as the change of windows causes the focus to change. The return of 0 as the current portal row suggests that this is what's happening. I had a situation where I was looping through a portal and performing a script, which called another script, and that third script temporarily opened a new window, put some information into a new record, and closed up again. I couldn't figure out why the portal kept resetting to the first row. Several hours of debugging showed me the problem. HTH, David
Create an account or sign in to comment