Let me tell you, however confused you are, I'm even more so.
You have files, all of which have their own various event-triggered code, among them, renaming themselves. They will rename and save themselves regardless of when, what or who opens them.
If someone opens one of these files that was made a few days ago, it will immediately save itself under a new name with today's date; but what if such a named file already exists? - there's danger of it being overwritten. Maybe you want that.
Here is the code that I have so far.
I note that in
Emergency log.xls you have two versions of the
Copycell macro; one in the
FORMS sheet code-module, and one in
Module4. It would help to know how you intend the
Copycell code to be started; manually,? automatically?, on the click of a button?
I suspect that you want to lose
Module4 altogether and keep the version in the
FORM sheet's code-module. You haven't
moved the line
Public wkb As Workbook '<< added line from the top of the
ThisWorkbook code-module to the top of one of the standard code-modules as suggested in message #22
I will look more closely at your files today/tomorrow, but not right now.
The password is ka3pmw all lower case.
It would help if you removed such password protection - just an unneccessary hoop for people trying to help you to have to jump through.
BTW the event spaning midnight is not a problem as it would be the date it was started.
Oh yes it is - your current cell-copying code looks for a file with
today's date (the date while the code is run ). If the file was opened by a user before midnight, and the cell-copying took place after midnight, the file wouldn't be found.
Of course, you might say, that would never happen, but it is easy to envisage one or two situations where it could easily happen; users (those very users, some of whom you say '
are lucky to fill it out let alone do a copy and paste') can leave files open at the end of the day and come back to them the next morning (they may have
had to, say in the event of a fire alarm and subsequent emergency building evacuation).
Coding is, in large part, a battle to keep things foolproof; the fools nearly always win.