>>I've started playing with Craig Boyd's VfpEncryption.FLL library. It works fine on my machine, but, after poking around the Web, I'm not sure that it will work fine in every situation where my VFP apps might be deployed. One writer noted that VfpEncryption is dependent on the following C-runtime files:
>>
>>MSVCM80.DLL
>>MSVCP80.DLL
>>MSVCR80.DLL
>>Microsoft.VC80.CRT.manifest
>>
>>Can I simply include copies of those files in my app's home folder, or will I have to go beyond that and require my users to step through a DLL registration process?
>>
>>-mark
>
>In case you're still working with this or someone else happens upon this thread. I explained how and where to install the VC++ 8.0 runtimes in a blog entry i made for the regular expressions FLL i created. Different FLL, but the information still applies for any FLL made using VC++ 8.0 (such as VFPEncryption.fll).
>
>http://www.sweetpotatosoftware.com/SPSBlog/PermaLink,guid,91241006-595a-487d-ac06-d0fc1fc71632.aspx
>
>The other way to handle this is to download VFPEncryption71.fll which uses the same runtime as VFP 9.0 (namely msvcr71.dll... although some FLLs created with Visual Studio 2003 may also require msvcp71.dll so I usually distribute both with a VC++ 7.1 FLL just to ensure that they are on the user's machine... in the case of VFPEncryption71.fll the msvcp71.dll is not needed). The best place to put the VC++ 7.1 runtimes is in the user's System32 folder which ensures that they are visible to the FLL/VFP during runtime... it's the easiest way to avoid the dreaded "invalid FLL" error that is so commonly run into when the runtimes are missing.

Thanks for the reply, Craig. My objective is an app that my 85-year-old mother can install without any help from me. So, after reading the documentation that you suggested, it seems to me that my best approach would be to add an Microsoft.VC80.CRT subfolder, put the 4 runtime files in there, and then confirm their presence as part of my app startup routine.

-mark