>The biggest problem that I currently see is a versioning problem between the controls the application was designed with and those installed on a user's computer. For example, if you design and release a product with one control and have that one installed. Later, after upgrading the control you must supply the user with both the executable and the new control.

This applies to any program, not just VFP apps, right?

>One of the nice additions to the language that can be used in this regard is the AGETFILEVERSION() function. In my situation, where the application is distributed over the network, I can keep a directory of the current controls, and can compare the version numbers between the one's on the network and the one's in the user's system directory. If a new version exists on the network, it's simply copied into the user's system directory.

It seems to me that this is best handled by the installer.