>>>>>Does anyone know of a fix for this problem. I would like to avoid having the "Covert 3.0 Resource File to 6.0 Format" question appear on the screen and somehow remove the potential for corruption of their Foxuser.dbf or the system modifying their shortcut.
>>>
>>>Do you have to have a foxuser.dbf for your applications? If so, you can give a different name to the one for each version and use SET RESOURCE TO in your startup program to point to the correct one.
>>>
>>>If not needed in the VFP6 version use SET RESOURCE OFF, or start up in a different directory from where the 2.6 foxuser.dbf is located.
>>
>>Another alternative is to use a different name for the resource file, and assing the name to use in the CONFIG.FPW for the application.
>
>Libraries like foxtools.fll should be renamed aswell.

The same applies to things like SUPERCLS, SDT, and your own class libraries - a few of the base class properties have different defaults, and some commands have different limits.

One trick I've taken from Doug Hennig's stuff is to create .PRGs that provide the same functionality as newer native commands; lets me use the newer syntax consistently. NEWOBJECT is a good example here.