Not to over-state the IntelliSense issue, but it's fairly easy to add your team's shared UDF's and objects into IntelliSense. After you do this, in a team environment, each developer gets syntax tips when using your shared libraries, not just those built into VFP. This can be a time-saver for developers who aren't completely familiar with the parameters required by your custom functions, for example.

Also, by writing your own IntelliSense scripts, you can automate "best practices" to improve code quality and readability. For instance, you can configure Intellisense to "expand" a typed word like "chg" into *- Changed by Bruce Allen on Feb. 5, 2002. These shortcuts help get comments into your code more often, and the bigger the team, the more important this becomes over time during maintenence. Much of this functionality is available with VFP6 using CEE - the Cob Editor Extensions. If you wanted to make a case for sticking with VFP6, I would recommend using CEE.

For most developers, the VFP7 upgrade is about time-saving. For me, it's worth the cost, but your mileage may vary.




>Thanks for all of your comments.
>
>I can see intellisense is favoured.
>
>Kev