>All,
>
>I am just starting to dig into a new project and was hoping to get a little advice on where I should start. I will be trying bind VFP code to a file write event generated by an outside application (not VFP). This app will be writing to a text file, and I was hoping I could trap this event without adding any code to the outside application. I am hopping I will be able to use VFPCOM.dll (or something inherent to VFP) to bind to a system level event, as opposed to using a timer object & poling the directory for the creation of a text file. I looked into the filesystemobject (Advisor May 1999), but from what I have read, I don't think it will do the trick.
>

VFPCOM will only help if the other application is a COM component of some sort and has an event that you can bind to; there's no generic system-level evnet model available to you to when another app does something and doesn't tell you about it. there's no 'system-level event' to bind to. The Scripting.FileSystemObject doesn't tell you what's going on elsewhere in the system; it provides a COM interface to a number of APIs, but doesn't server as a general purpose IO monitor.

I'm afraid that either your application will have to poll, or the other application will have to signal the event to your VFP application using something like MSMQ, to let your VFP application know when something happened.

>Any advice on getting started is greatly appreciated.
>
>Thanks In Advance,
>
>Nat-