Hi Sergey,

I decided to try the cryptoapi class. There is an example form using the cryptoapi class provided under foxpro foundation classes in the sample solutions. I added cryptoapi to my project, drop it on my payroll form and tried to encrypt the amount field of the payroll transactions. I was not able to encrypt this numeric field. Evidentially, the cryptoapi class is designed to work more with text and strings, so I changed the encrypt field to description which hold description of the transactions like Regular Salary, Overtime, FTW, and employee name on Payments, and it worked great. I tried it on an employee transaction table with around 110,000 rows, and it was a little slow. Anyway, it appear cryptoapi would be useful in the right situation, so I left it in my project.

I still think the best solution would be to create a special group, and assign a share folder to allow access only to this group. Then give only user that should have access to the folder the group privilege. Also, I suppose I could create a special user/password, and assign access to the shared folder only to this user. Then give only users who should have access to the folder the username/password pair and let them login as necessary. I would change the username/password pair often and re-distribute it to current user who need access to the folder. I also use a Linux share for FoxPro Tables. Security can be by user, by server, or I can have the Linux box join the windows domain. The security under a samba share can be configured to be better than windows security.

LelandJ