I'm not crystal clear on the meaning of your post, but I know this: let's say you have a list of 10 records and the focus is on record #1. If you omit record #1 the focus is then on the "new" record #1 (the former record #2). This is especially important when using a script that omits or deletes records. The script would , let's say, omit a certain record "If" certain conditions are met then "Else" go to the next record. This prevents records from being skipped and therefore not evaluated.
I have also recently converted a database from FM9 to FM10v3 and have experienced a similar problem. The main window has numerous records in list view. Each record has several portals. When a change is made in a portal of one of the records, the window now scrolls so the active record appears at the bottom of the window. This did not happen with FM9. Hope there's a way to change this behaviour!
We've been having this issue too.
Does anyone has a solution to this?
Hmm, R12GS refers to omitting a record from a list view. BRG describes modifying a record in a portal. Seems like two different issues.
nese, which issue are you asking about?
With regards to List Views, Filemaker 10 added an "auto-sort" "feature" that has triggered a lot of complaints including some from me. If the layout's found set is sorted and you edit a field that is part of the sort order, comitting the record resorts the records to place the comitted record in its proper place. This can result in records "jumping" to completely unexpected locations. Could this be a factor here?
I'm asking because when I omit a record from a list of records, List View Or Table View makes no difference, omitting the record does not result in the window scrolling nor does the last record in the list become the active record. Instead, the next record down on the list becomes active and all versions of Filemaker work this way as far as I know.
I think we need a more detailed description of this issue in order to better understand it.
For a large found set a couple of pages long, when I omit a line in the middle found set (let's say on the second or third page of the found set) it bumps the cursor to the next line and pushes the cursor to the bottom of the window, which make it hard to follow where i was.
I've sorted the found set before doing the omit record. And this only happen when I omit something where the scroll bar is not on the top.
Got it! The key detail is that the window is not scrolled to the top. I can reproduce this in Filemaker 10.03 advanced on Windows XP.
Sorting is not an issue. Works the same on table and list views.
Can anyone else confirm this on other operating systems/other filemaker versions?
Edit: Just confirmed that this is only true for sorted lists, so sorting IS a required element to see this in action.
I am on Mac (tested on both 10.5 and 10.6) and it happens too, whenever the scrool bar is not stuck on top, the omit record will jump the cursor to the bottom of the view window.
This does not happen when I am on filemaker 9.
Sounds like enough information to make a bug report in the "report a bug" forum section. Once such post coming up. Feel free to review that post and chime in if I leave something out or make a mistake.
Today I discovered that the window scrolls (upon an OMIT) with a SORTED list.
If the list is un-sorted, omitting a record does NOT scroll the window.(I added this detail to the Original (TOP) post today Jan 19, 2010)
Thank you for your posts and narrowing down the problem.
I have replicated the issue on both Windows XP SP3 and Mac OS X 10.5.8. I have forwarded this information to our Development and Software Quality Assurance (Testing) departments for review and confirmation.
This also happens in either FM 8 or 10 Advanced (the 2 versions I have) when doing "Show All" after a Find or using the script step Scroll Window [To Selection]. Rather annoying. An active (selected) record that was at the top of the window finds itself at the bottom of the window after the action.
Hopefully FM will solve this for FM10 users.
Filemaker 11 does not have this problem. Luckily my FM10 purchase came with an upgrade option so I'm now running FM11.