In my multi-file system many of the files are related which seems to keep 'closed' files on the hidden window list. So the closed files are never really closed - merely hidden.

I also use $$vars to track a users movements, but it seems that when a file is 'closed' (but retained open for related reasons) the $$vars persist, whereas I expect them to have cleared because the file was closed. (Back in pre FM7 the files did actually close and I used global fields to do the same tracking)

This in turn makes a mess of my opening scripts which are relying on some of the $$vars. For instance there is a 'home page' layout for every file which is the one to go to if the file was closed, but it is better to return to the previously used layout as this has the previous record set on display.

I made myself a workaround by deliberately assigning a $$var to the current layout name when closing the file which, because the $$var persists, still has the last layout name I need. So when the opening script checks for the last layout it will go to it.

The interpretation of when a file is 'closed' is open (:-D) to debate.

Bug???

The curse of the global variables declarations indeed! Thanks for sharing the expirience, yet another argument for extensive utilization of script paramters and script results as Janet Tokerud showed in her blog, here enhanced further by our Comment:

http://fmforums.com/forum/showpost.php?post/187787/

Furter read on the topic:

http://www.fmforums.com/forum/showtopic.php?tid/188219/fromsearch/1/hl/tokerud/tp/0/all/1/

--sd