>>That can be done from code called in the startup code, as defined in one of the options in config.fpw. Here's a line from my vfpstart.prg:
>>

STRTOFILE(TEXTMERGE("*--<<DATETIME()>> - <<SYS(0)>> ")+0h0d, HOME()+"_command.prg",1)

>
>Yes, we do something similar (but data driven so each of us can have different startup line(s) in our environment.
>
>(mine looks like this, which is the default not-customized)
>
>

>*********************************************************************************
>*Session started for Monday, May  6, 2013
>*********************************************************************************
>

I went minimalist, with a single line, because these tend to accumulate. And I'm alone on this machine, so I don't need personalization. However, I have an intellisense macro for inserting comments:

lparam oFoxCode
oFoxCode.ValueType="V"
lnHours=SET("Hours")
set hours to 24
lcSetDate=set("date")
set century on
set date ymd
lcReturn= "*["+ttoc(datetime())+"] " +getwordnum(sys(0),2, " #")+ " -"
set hours to lnHours
set date to (lcSetDate)
return lcReturn

which is nice for recognizing different people's signatures in the code. And I put the datetime just to sound official and like a real programmer, only to realize, to my surprise, how extremely useful that datetime is. Just a few months down the road, knowing when exactly a comment was written means a lot.