Glenn Christensen wrote in a message to All:
GC> Here's something, if not exactly a bug in Max, one should be aware
GC> of. 
GC> My callers are giving the access level of LIMITED on their first
GC> call. Recently, while testing something unrelated to this, I
GC> downgraded a a name to TRANSIENT in order to make some local
GC> log-ons. After entering the password the line, "NOT A VALID FILE
GC> AREA," (or the one similar to that) popped up. Here I was trapped. I
GC> couldn't get out of this, and no matter what file area I selected,
GC> the same line kept popping up. After a couple of warm boots, with
GC> the same results, I upgraded the name to LIMITED and the problem
GC> went away.
 Your problem there is that the last file area you were in is set to
 an access level higher than Transient.  So your pointer points
 to an area you can't get into or see.
 Hence the 'not a valid file area' notice.
 Upgrade yourself, change to a file area that Transient users can see,
 downgrade yourself, and it will be fixed.
 The same thing can also happen with the message areas, by the way.
 GC> So, it would appear, one cannot assign an access level below what
 GC> one gives to first time callers.
 Not at all!  You just can't access file/message areas below where
 you should be.
 Another caveat: in Max.ctl, you'll see settings for Default file and
 message areas for new callers.  If you set those areas with an access
 level above what new callers actually get, they will also see this
 warning about invalid areas.
 Hope this helps!
 Patrick
--- timEd 1.10
---------------