But in the end - there is nothing to stop somebody from opening the raw dbf's - unless the laptop runs like a kiosk.

fwi - security is always an issue. What may or may not be an issue is whether somebody wants to address security. For instance, security is an issue since you do check some basic authentication information.


>I have considered the security aspect, but it's not an issue. The compiled part of the program has a method that gets the make,model,username and cpu serial number. It those things don't match with those in my system, I can disable the laptop.
>
>John
>
>
>
>>>One of VFP's strengths that I am taking full advantage of though, is the ability to put code in memo fields and compile at runtime using exescript. This way I can modify the code and not have to recompile when I make changes to a large part of the program.
>>
>>John
>>
>>How about the security of that approach? Besides the obvious hacking with nonsense, that wouldn't compile, there is always the use of dangerous commands like drop table or zap. But worse could be changes that are hard to find, like changing a statistic or someone's salary or review type of thing.
>>
>>Have you considered these issues? Is the code in memo fields kept in the clear?