>Well actually, there are many ways to secure data from hackers, but what I am after for is to see that the DBC have its built-in security whether it's installed in a server or stand-alone PC. Because once the DBC/Tables is outside the OS (server/client), it is already vulnerable to hackers. And that's basically the a big hole in VFP's marketing strength, because clients wants security without much intervention on OS.

Jess,

If the files are not protected from access how would you propose that the DBC be secured? If I can get at the file on the drive I can hack into it, password or not.

I did a presentation regarding security in applications last year in Frankfurt. In that presentation I looked at a lot more about security than a password on the dbc. One needs to:

1. analyse the source of the threat
2. analyse the thing being threatened
3. analyse the potential loss from a breach
4. analyse the cost of implementing security against that threat keeping in mind who the threat is.
5. then and only then can one determine the security level needed.

There are third party products out there that will encrypt your data for you. NT or Novell can protect the data by rights assignment. Files can be hidden, the dbc dct and dcx can be built into the exe and not distributed to the user's machine at all.

I understand that security is on the wish list, but for me it is way down the list.