>>I am almost finished writing a scanning utility to highlight all references to date/time functions in prg files across a whole disk
>
>Interesting. How about tracking other variables involved in the statements?
>Like cDate = DTOC(DATE())
>Then later in the code cYear = RIGHT(cDate,2)
>
>If the tool can't track things like this, then it gives a false sense of security.
>I decided that I didn't want to write a VFP parser and cross-reference tool myself, so I'm waiting for a solution...

Paul,
My utility finds all references to 'date', 'time', 'year', 'dtoc', 'ttoc', etc. whether they be functions, variables, fields, or whatever. ANY reference will be counted and the program highlighted with the number of references found. In your example, the program will be highlighted with FIVE references in just the two lines you give, plus ALL other references to those variables. It can also select programs by the last access date and highlight any PRG files missing where the FXP has been accessed recently.