Hi David,

You will not need to convert any of your current data to run VFP 7, even though additional functionality/stability has been added in this area. In VFP 7, procedure can be run in the DBC when it is opened and when it is closed.

When you run your app in VFP 7, a wizard will ask if you want to convert your menus to VFP 7 format, and warn that doing so will make your app incompatible with eariler version of VFP. If you plan to upgrade your client base to VFP 7, you can have the VFP 7 wizard update your menus and this will give you additional functionality like the ability to add bpm pictures beside menu options.

When compiling your app with VFP 7 you may get an error message regarding lines in your form methods/events that warp to a second line. This can easily be corrected by adding an simi-colon to the line that is wrapped.

Also, if you are using arrays, you may need to change the syntax of the define array line.

I encountered all of these during my conversion and would describe them as very minor update issues. All in all, my conversion from VFP 6 to VFP 7 was the easiest update I have every done. Most other updates usually involved some code changes that caused me some major headaches and required a scan of the app with filer to find the code that needed to be updated.