>Hi,
>
>Does anybody has any experience with protecting a table (free table, database) with a pasword.

You have (at least) two approaches available to you. The first, which works in a cross-platform fashion, would be to encrypt the file in some fashion using a third-party product; it would be the responsibility of your application to provide encryption and decryption at runtime based on passwords/user identities or whatever.

If the file resides on a machine running Windows NT, and the file is on an NTFS partition, file access rights can be assigned on a user-by-user basis; the operating system will take care of enforcing access permissions on a user-by-user basis. This could restrict access in several ways automatically; some users could have full access, while others had read-only access, and yet others could simply be blocked from reading the file at all - the operating system takes care of the access permissions, and you'd simply have to trap errors that might occur as a result of file permissions in your error handler.

As I recall, permissions can be assigned to files on a file-by-file basis under NetWare 3.x and later as well, so it's an option for files residing on NetWare servers as well.

If access control beyond the file level (field level restrictions, restricted record sets, etc.) exist, you'll need to use a database backend like SQL Server and move away from native VFP tables.