>Upgrading VFP5 to VFP6+SP3: Is there a business arguement, or only a developer's convenience arguement?
>

Just going to VFP 6 - the Y2K features might be the most compelling reasons. SP3 added better COM Support... It is one of those no-brainer upgrades. You VFP 5 stuff works as-is....

>Should projects be designed so the user interface components can be stored/launched locally rather than over the network (where the data must obviously be stored)? This seems like a simple solution to the long lag-time from double-click to first screen update, at the expense of easily updatable form functionality.
>

I am a fan of locally stored EXE's and support libraries. COM Components are another issue alltogether...

>What VFP methodology would you use to coordinate sales and payroll information from 12-15 branch offices into the corporate environment?
>

I am not sure there is a VFP-specific methodology here... Are you asking for advice on how to build such a system.... What data store to use...etc...????

>Is there an easy way to debug macro expansion?

Short of looking at what the variable is, and testing it to make sure a syntax error is not lurking around, no...