Thats not a bad idea. Same as Alex's iro including the fll in the project. But this would work for a dll as well. Worth thinking about ...


>Hi jos,
>
>What about including the fll into the executable (store it into a memo field of an included table), extract it to a temp file with a random name and directly calling it after you placed it on disk?
>
>Walter,
>
>>Hi Craig
>>
>>iro your VFP encryption library - because one needs to pass the password to the encryption/decryption routines would an attacker not find it quite easy to substiute their own dll/fll for yours and then intercept the password when the routines get called? Is this a possibility for attack? If so, is there a way around this perhaps by setting up the password in the main app and the dll/fll looking for it under a static variable name or something like that? Or do you feel this an unlikely scenario?
>>
>>Thanks.