>>>>>Do I need to break out the CD-R disks again to send out another version of the VFP files to my users, or can I just send out a freshly compiled copy of my EXE? Thanks in advance.
>>>>>
>>>>
>>>>You need to send out a new runtime.
>>>
>>>Excuse me for jumping in...
>>>
>>>I normally distribute applications by creating a setup program with the setup wizard. I will prepare a new setup with SP3, however, will I need to rerun my new setup on all PCs or can I simply copy specific files to specific directories, including my new .EXE to each PC? I would like to avoid running the setup program on each client.
>>>
>>
>>You must at a minimum install the runtime on each target PC; copying the files in place is not adequate because of updated shared components that will end up in the Windows System directory and registry updating. I haven't tried running an .EXE compiled under pre-SP3 VFP6 under the revised runtime, but I'd assume that the executable can remain the same. There are changes in the dependency files in the SP, so if you rolled your own install without the Setup Wizard, you'll need to re-examine it.
>>
>Is there a way to determine which version of FoxPro and Service Pack are running at run-time. When my application starts, I would like to verify if the latest service pack has been applied and if not, display a message to the user to recommend upgrading.

It's pretty easy - VERSION(1) returns a string containing the exact build information for VFP.