If it's another table that you want to update, create an Update Query that references the calculated value and use RunSql or Currentdb.Execute to fire the query.
Everyone else makes a good point about not saving calculated values though, but sometimes needs must.
I'm not a laptop at the moment but if I remember correctly certain controls have a Context menu property where you specify the name of a context/pop up menu to allocate to the control. Access handles the rest.
Following Gasman's advice, subsequent calls to the Dir() function gets the next matching file path.
By the way instead of copying the file across and deleting it, you could move the file... same process as cut and paste.
Oh I see. You can't run that sub in the immediate window. Only public functions or subs in a Standard Module (not a Form Module) can be run from the immediate window. You can however put a break point in the sub and test the initialised variables in the immediate window when it breaks.