Well, this is what I need to know. I'm ok on the modifications, because I tested the VFP7 version by first copying my entire project to a separate directory, so I have a fallback after make any irreversible changes.
Kind of annoying that there are even MORE runtime files needed, but it's not a showstopper. Onward and upward, it seems.
Thanks,
Randy

>You have an App/Exe that now requires the VFP7 runtime AND VC runtime files. See the VFPDEPLOY.DOC whitepaper in the TechnicalArticles folder of the VFP7 installation CD [or download].
>
>Everything should work. However, 2 components will not have been altered unless you explicitly do it yourself. One is the VFP menu. If you Modify Menu, then your VFP6 menu gets converted to the new VFP7 menu format which now allows you to identify a BMP image with menu options. These menus can no longer be modified in VFP 6 unless you open the menu table file exclusively, modify the structure and delete the last 2 fields, sysres and resname.
>
>The second is the database container. Once you enable DB events, the DBC can not be reverted back to VFP6.
>