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

For clarification, I am in particular with DBC/Tables not only on DBC because we are after the protection of the contents which are informations.
And granting hackers have the data but it can not be opened or read it without the password. And that's the basic needs for security.

>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:

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

Why the need for third party tools, when M$ can include it with the product? IMHO, it is abnormal to include DBC/DCX/DCT with the EXE.

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

We lost 2 projects because of the problem alone. For us as developers, it does not matter to us, but a lot client are saying that there data are not secured with VFP DBC/Tables that's why they are asking for it.