Procedure Execution life

[Elon Close]

I have 2 DB, DB1 & DB2
It is easy to confused but the below seems to be the case.

a DB1 window is the front, active window, the only window open in DB1
This is ensured by a DB1 procedure that is running
This DB1 procedure then executes
SelectAll ; to insure that all records are visible for the following  
statements
Save      ; to save DB1,  probably redundant with the next statement
SaveAll ; to ensure that any changes to DB2 are saved,
CloseWindow
stop

At this point, as far as I can tell the only open DB is DB2
its open forms are still there, nothing has changed for them,
which is what I might expect since I have essentially nothing
open  for DB1 which shows no forms and is not secret.

If instead of stop I have
CloseFile ; which closes the active DB, which I would expect to be DB1
then DB2 is closed out, which is ok with me

But this indicates the statement is acting on DB2 since it is closing
the “currently” active DB. It seems that a procedure continues to run  
even
after the DB which contains its source code is “closed“.

In other words Panorama runs the procedure to completion and if the  
actions
pertain to the active DB, that DB is not necessarily the one that  
contains
the procedure. This is OK with me, but a little unexpected.

It happens to be that this closure of DB1 and DB2 is what I wanted.

Elon