Any clues, Profoxers? I realize it's the weekend and you all have
lives, but hopefully one or two of you don't (and can help with this
one). :-)
On 2014-05-17 17:14, [email protected] wrote:
I developed my app on Win7; works great. I move it to an older WinXP
computer for some not-my-machine testing...it fails with an Error 1691
on the SET LIBRARY TO VFPEncryption71.fll line. I researched the
error and found this on Craig's site:
http://www.sweetpotatosoftware.com/spsblog/2009/08/09/MajorVFPEncryptionUpdate.aspx
'If you are getting a "FLL is Invalid" error when running either of
these FLLs it is because you are missing the runtimes on the system
you are deploying your application on. What about the previous
vfpencryption.fll that used the VC++ 8.0 runtimes? I continue to
update to the latest Visual Studio (10.0 will be next) and I suggest
you do the same. Most VFP developers are using the vfpencryption71.fll
as the C runtime matches the one used for VFP 9.0 (msvcr71.dll) and it
provides the exact same functionality as vfpencryption.fll.'
I just went and downloaded the latest onto the test machine....same
error.
My VFP runtime files are right there in the application's folder,
which is c:\MBSS\FabMate, along with the latest VFPEncryption71.fll.
Ideas?
tia,
--Mike
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
