You can just do not enable DBCEvents on the DBC. Also, if you have to use the Menu Designer to modify a menu, open the .MNX file exclusively after you are done and delete the last 2 fields [sysres and resname] IF you need to go back to a menu version prior to VFP 7.

As always always develop on a test copy of the database. Before deployment, test the new app components on a non-developer machine along with the old components that have to co-exist with the new. Do this testing with a test database as well. Once successful and you know the old [those not yet replaced]and new components work, deploy to production system.

>I have a client with an existing VFP 5.0 application, compiled, it appears, using Refox, so that it cannot be decompiled, original author is gone, you get the picture.
>
>They are interested in redeveloping the application, as well as extending it to the web and other integration points, for which VFP 7.0 seems ideal. Question is, can VFP 5.0 and 7.0 share DBC/DBFs without corruption or other problems? Ideally, this would allow us to build incremental functionality to replace the existing software without having to do a massive (and doubtless, painful) cut-over. We could actually even use VFP 6.0 if we needed to to get compatibility, and would give some added stability over the existing solution at least.
>
>Comments and suggests always appreciated.