>>The purpose of the timer is to see if a file hit a folder and then to act on it. I'm trying to extract the bind events in the VFP 9 Windows Events in the Samples and it, the event binding, seems to work.

The one I recall is under VFP9_install_folder\Samples\Solution: run solution.app (or solution.scx) and under "New in VFP 9" the last option should be "Binding to Windows Message Events." There's a sample on detecting file changes in a folder. Sorry if that's what you're referring to, but no timer needed; whenever a file appears, the Windows message is detected by your app. So you can just leave the app sitting at Read Events or something like that, waiting for a file.

You can detect when files or directories are added, updated or deleted to your system using Windows messages.
Sample: to run the sample, click on the Enable Event button. Once the event is active, open up Windows Explorer and try adding, removing or renaming a file or folder. You can also change a file’s attributes such as making it read-only.
Details: 
This sample uses the following binding to handle file detection:
BINDEVENT(_VFP.hWnd, WM_USER_SHNOTIFY, THIS, "handlewinmsg")
Note: WM_USER_SHNOTIFY is based on the WM_USER message
In addition, this sample uses a number of Shell functions to detect changes to files and directories.         
You can find additional information about shell events in MSDN:
WM_USER Message
Shell Programmer’s Guide
SHChangeNotifyRegister function
Click on the Constants button to view values for the #DEFINES.