Actually in this scenario that you are outlining, I would actually come back
and ask how did you set what letter name the users supposed to get? And, at
what point in the program or user interaction did this setting of the letter
occur?

The reason why I'm asking the above is, instead of having one big processing
loop that goes thought the "dayfile", you could simply Call the
mergeNoPrmpts WHEN your code adds a record to the dayfile (or, more
importantly when you actually set what letter going to be sent out) . That
way, you have all the documetns created and no "extra" process to be run at
the end of the day. It also not clear if dayfile is to be the data source
for the word merge, or if datafile ONLY has the "id" + letter name for the
user?

If the data source is different than what you could do, is when you write
out the dayfile, you would call MergeNoPrompts, and the add the actual
document name (with full path name) named that merge no prmopts created to
your day file table. What this would mean is that you could actually merge
document from different forms and even different data sources.

for the time being, let's ignore the above suggestion an approach.

We can simply write some code that would process the day file as you need.

dim    rstDayFile      as dao.RecordSet
dim    strSql          as string
dim    strSqlforWord   as string
dim    strDirPath      as string

strDirPath = "C:\Documents and _ &
      Settings\Mark\Desktop\NewGen\Word\

strSql = "select * from DayFile order by id"
set rstDayFile = currentdb.OpenReocrdSet(strSql)

do while rstDayFile.Eof = false
  strSqlForWord = "select * from dayFile where id = " & rstDayFile!id
  MergeNoPrompts rstDayFile!LetterName, strdirPath, True, , strSQL
  rstDayFile.Movenext
loop
rstDayFile.close

Notice how the above loop has to actually specify the correct SQL, and
select the one record that we need. I'm assuming that you have a primary
key, or auto number field of ID in this list.

I've also never tested this code in a loop, and my spider sense tells me
there's going to be some order of printing problems because of the way word
prints documents out. I know how to fix this problem, but I guess you can
give the above a try and see how well it works. Note that the above code is
what we call air code, and I simply typed it as I wrote this message. So the
above is not tested, but it should give you the general idea as to what you
need to do.