>>Pass the info through a .DBF file that your VFP app is periodically checking for new records to process, by using a timer. You can put in this table anything you need from the FPW side. Just make sure you create this table using FPW, not VFP, or FPW will not be able to access it.>>>>
>
>Fred, thanks for information.
>To get this clear, would the following be the way to go:
>
>1. Load my FPW app
>2. Get the FPW app to load the VFP app (proably at the start)
>3. In my VFP app, I have a timer which just constantly loops around checking
> for records in a TEMP file.
> ..When it finds them, process them and delete the file
>
>Does this mean that my VFP app is always running..and will this slow sown the pc in any way. ?
>
>Regards,
>
>Gerard

Sounds like you've got it on the right track. I just wouldn't use a temp file, I'd use a real table, and process the records from that table. On the VFP side, I'd scan through the non-deleted records, lock any one that needs processing, mark it for delete. On the FPW side, I'd look for a deleted record and re-use it, and if none found, add a new record. Either way would work, use whichever way you're more comfortable with.

If your VFP app is firing off of a timer, there shouldn't be too much system overhead beyond the fact that you have a VFP app taking up memory. For the most part it should just be sitting at the READ EVENTS, doing nothing until the timer fires.