>Will VFP6 and VFP7 co-exist happily together when it is released.

On the same machine? Yes, as far as I can tell. If they change the final version to upgrade your VFP6 instead of install next to it, thats a different thing, but I dont' know if that will happen.

>I may want to move the existing apps into VFP7 I presume this will just mean recompiling the apps in VFP7 and sending out new setup disks. I am right in this assumption.

Well, you might wanna test too :-) There are a handful of changes, that will most likely be in the help fuil (Behavior changes since VFP6). Like what you say? The way the _screen and _vfp dimensions work have changed, also, if you missed any commas in a LOCAL (ie: LOCAL lcApp, lcPath lcINI) that will fly in VFP6 but not VFP7 (you're build will catch that though).

>If I do send out new setup disks I am hoping that by not including my data folder on the setup disk I can avoid having to make a copy of the old data and appending it in. Is this right. Does setup work in this way. If it does will my old DBC container/tables work with the new VFP7 exe.

If you're data structues are changing, find a utiltiy that handles that, like SDT. Great stuff. OTherwise, VFP7 (as of right now) apps can use VFP6 data just fine, no need to redistribute that.