FMP7 forgets sort and last layout

[john902]

I may give up on FMP7 after all. It is back to forgetting both its last sort and layout. For example, I hit ctrl-j to show all records, put it in either List or Main view, sort with most recent date first, put with the cursor on the top record, and close. When I open again, it's in List view (whether I closed in List or Main) with the cursor way down in the middle of the database, and sorted to an old, previous sorting order.

I had this problem before; at that time I removed all scripts and button assignments before converting the file from version 6 to 7, and that seemed to fix it. But now, with no scripts added (button assignments put back in), the problem is back again.

Does anybody have any ideas? I hope so, as I've found that FM Support ignores requests for help. I'm trying to be patient with FileMaker and would like to stick with it, but if things like this keep up I may drop it after all and switch to something like Approach.

Thanks for help!

[Ugo DI LUCA]

Hi,

Check the Opening Layout and the Opener script you decided to be triggered at opening of the file.

In the Options Menu.

It can be that your previous version had a script or that FM decided itself for a default Layout when you updated.

[Deep Thought II]

strange... didn't filemaker prompt u to save current layout setting while u switch between form and list view? mine does...

although i haven't done extensive testing for the problem u mentioned... it's nice to have a layout specific for tablie view, and another one for list view. or use script step to control switching between views instead of using menu.

i kind of dont want the users to manipulate around all of filemaker's features. instead, i set what's available for them for each forms and layouts. i think this is better than switching views from the menu.

i am used to have a button on a Form view, that says, "View as list", and then it goes to list view when pressed... and at the same time u can set sort for the specific form too~

[Robert Kidd]

Ok this is how I understand the status of a database on opening:-

The layout is determined by the layout as set in the "File Options" menu

it dosn't remember the layout you were on when the file was closed.

If you don't specify a layout in this option it will default to the last layout viewed in layout mode.

Sort order is always creation order.

Found set is the found set on closing the file.

Current record is the first in the current found set.

All of the above can be modifed by running a start up script. If you want to return to the last layout you viewed ( variable ) in the last record you viewed I think you would have to create a user table which stored this info using a close script and restored them with an open script.

[john902]

I wonder, though, why this has only begun to happen--in my experience, anyway--with version 7? Version 6 always returned to exactly wherever I was when I closed--I got used to it; it was convenient. But now, 7 seems to open wherever it feels like. This is with no startup instructions or scripts. The setup is just plain vanilla, as it also was in version 6 except for the go-to-layout buttons. Now, in 7, a sort order and a find from some time back seems to be stuck in memory. It seems erratic, fixated on a setup it should have dropped, though maybe it isn't, but is just something I don't understand. I've managed to use scripts to have FM open the same way every time, now--with all records showing in list form, sorted by date, descending--but I miss the convenience of being able to do something with a certain find and sort, etc., exiting, then popping aback in to continue where I left off. From versions 5 and 6 I had thought FM was basically, without scripts or anything, supposed to open just like it closed. I wonder what's what, here. Has version 7 simply been changed? Or was something quirky or complicated or accidental making the earlier versions act one way and version 7 another? Thanks for hits and help; I'm kind of lost, here, and a little bit disappointed that version 7, even though it's heavier-duty in some ways, isn't, so far, as easy or pleasing for me to use as the older versions. In face, it threatens to give the feeling I've had too often with new software--that the upgrade feels more down than up.

[Arrakis]

In FM 6 and earlier, opening a local file will modify it even if no changes are made to the database (for example, browsing some records, doing a find, sort, etc.). This was an issue because it meant that it wasn't possible to tell how long it had been since changes had been made to the file by looking at is modification date. It also meant that backup programs would see the file has modified. This was corrected in FM 7 so that if you don't make any changes (again: browsing records, finding, sorting, but never modifying any data or schema), then the file is left untouched, unmodified. The downside is that this means your last found set and sort order won't be saved when you close the file unless you make at least one change to the file, like modifying the contents of a field. If this is an issue, you can make an On Open or On Close script "touch" the file by modifying the contents of a field (even a global field). Since the file is already modified, FM 7 will save your last found set and sort order on closing the file.