>On the VFP site might make it easier to overcome the hurdles. But I don't see how putting something on the windowsupdate site would tie it to the some other release schedule. Seems whenever the vfp teams creates updates and/or new version. A runtime package is created and put on the site.

Not speaking for Ken or Craig, but I sure can see how outside scheduling, and more, comes into play...

1. Testing for Windows distribution has to be far far far more thorough - in terms of permutation/combinations of software and hardware components - than is required for non-windows-dist. stuff. This is not to knock the VFP Team's testing but rather to say that WINDOWS carries implications far wider than stand-alone distribution.
Take for instance, video cards. VFP is known to be "intolerant" of some, and that wouldn't be permitted for a Windows dist.

2. The above means far more staf work for the VFP Team.

3. The notion of Windows folks simply 'grabbing the latest that the VFP Team has produced doesn't really work (see above).

On the other hand, I sure LIKE your idea and continue to hope that it can someday be done.

cheers

>
>Kirk