I've just converted my app from 6.0 to 7.0. There were a few "gotchas", so test, test, test. Some internals of VFP 7.0 have changed and required reworking some of my 6.0 code. For the most part, (they say 99% compatible) you won't have any problems. I don't see any point in developing with 7.0 and releasing with 6.0 since your project has yet to be released.

I converted to 7.0 because I wanted to take advantage of "using the new "toys"". Execscript() in particular, but also many other features of the new language. My advice: the change is worth it.

My biggest problem with 7.0 is you can no longer create "temporary" indexes of tables in a read only DBC. (read non-structural, i.e. INDEX ON TO TEMP.IDX). This worked fine in 6.0 but doesn't in 7.0. My solution: free tables. Not the solution I would have sought, but workable.



>I was just handed a VFP 6 project that is half completed (still under development and nothing installed at client site yet). Can I continue on with this under VFP 7 and start using the new "toys" I learned at DevCon, or am I stuck with 6 for the remainder of the project ???
>
>I have read here in on the thread where you can modify a 6 project under 7 and distribute it with the 6 runtime files so long as you don't use the new keywords. But since it has yet to be installed, I want to continue with this project in 7 and distribute it with the 7 runtimes.
>
>Please let me know what you think.
>
>TIA !!!
>
>Jace