Silly answer!! --> No, they're weren't included in the project (since I ship them separately as they can't be included in the EXE) but yes, adding them to the project (excluded of course) fixed this issue.

Thanks, Richard!
--Mike


On 2014-04-30 10:41, Richard Kaye wrote:
Silly question time. Is the FLL in your project? Even though it's
excluded that may tell it where to find things? It's also possible
that it can't find the C++ runtimes required by Craig's libraries.

As a side note I tend to avoid the use of LOCFILE() in my distributed
applications and set the actual path to where the library (or table)
should live in the production environment. It's highly doubtful that
my end users would be able to make heads or tails out of that dialog.

--

rk
-----Original Message-----
From: ProfoxTech [mailto:[email protected]] On Behalf Of
[email protected]
Sent: Wednesday, April 30, 2014 10:42 AM
To: [email protected]
Subject: "Unable to find unknown HASH" (or CreateGUID or other FLL
functions) during EXE compile

VFP9SP2 on Win7

I'm using Craig Boyd's VFPEncryption.FLL and when compiling my EXE,
the compiler complains about the FLL's function calls.  I'm using it
in code like this:

SET LIBRARY TO LOCFILE("vfpencryption71.fll") lcHash = Hash(tcPassword
+ lcKey,liHashType)

I know some guys create dummy functions to get around this as I
recall, but isn't there a cleaner way?  I tried the EXTERNAL PROCEDURE
command but that didn't fix it.

Thanks,
--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.

Reply via email to