I think you are misunderstanding the process.
If you open the file when it is located on your computer and you are the only user, you should find these "details" exactly as you have left them.
If the file is hosted from FileMaker Pro or Server and you connect as a client, the layout, found set etc are not retained the next time that you open the file.
It could be possible to store this info at the time you close the file, but this process would require logging this info in a record in a table and then, when a user opens the DB, a script would need to identify the user, find the correct record and use the info stored there to recreate the "state" that the file was in when they closed the file.
But this would only be the case on a hosted database wg
That's not actually the case - I AM on my own computer at home, where I noticed the behaviour. This is an extract from the Help file :When FileMaker Pro doesn’t save a fileIn FileMaker Pro 6 and earlier, opening and closing a file would cause the file to be saved, even if you did not make any change to the file. In this version, the following actions do not necessarily cause the file to be saved:••If you perform any of the above actions without also performing an action that does cause a save (such as modifying data), the file won’t be saved when you close it. FileMaker Pro considers the above actions to be minor changes, and they aren’t saved with the file unless the file is also modified in a more significant way.For example, if you open a file, perform a find, and then close the file, FileMaker Pro does not save the found set with the file. However, if you open a file, add a new record, perform a find, and then close the file, FileMaker Pro will save the found set as well as the new record with the file.
But that only applies if this minor change is the ONLY change made. Any other change, such as editing a record will result in the file being saved and that will save the current layout, found set etc...
So you could just always modify a record and commit the change before closing the file. This "modification" can be a step that modifies a field by setting it to the value that it already has. This can be scripted to take place "OnLastWindowClose".
I find it extremely unlikely that I will open a database and only do one of these "minor changes". There's almost always some other data entry task that needs to be done or there would be no reason to open the file.
Oh I often do it! For example, I'll open my main collection database as a result of someone posting something in the hobby forum I'm a member of, find my own example of that particular item, see where I bought it, how much it cost me, then close without doing anything else.