I have a situation where I would like to be able to password protect only a few records of a database . Is this possible. also is there a way to let the password protection go after a year and find its release from a site maybe with an atomic clock so it would be accurate.

thanks

Yes, that's all possible by creating privilege sets with calculations to limit record access.

is there a way to let the password protection go after a year and find its release from a site maybe with an atomic clock so it would be accurate.

Atomic clocks are accurate, but you'd still have to take relativistic effects into account, for example, the altitude of the user, or the computer being driven around in a fast car.

LOL I see but I am in need of a way to password protect something in fm and be guaranteed it might not be opened for 5 years for example. I thought the only way to guarantee that time was to use an atomic clock setting online ....

Just add two number fields in your table and name them "_rightEdit" and "_rightView".

In the privilege set in record access, select the table you want to protect and under the view column, select limited.

Add the field _rightView.

Do the same for edit.

So when the admin put a checkmark in the _rightView field, everyone has access to the record. If there's none, the user won't be able to see the record. Same thing for the edit rights.

HTH

LOL I see but I am in need of a way to password protect something in fm and be guaranteed it might not be opened for 5 years for example. I thought the only way to guarantee that time was to use an atomic clock setting online ....

Well, if you can guarantee the service will still be there in 5 years, perhaps you could use the web viewer to get the date from it and compare it to the date stored in the record.

OTOH, a skilled hacker could probably intercept the query and point it to a spoofed site...

Edited August 14, 200916 yr by Guest

LOL I see but I am in need of a way to password protect something in fm and be guaranteed it might not be opened for 5 years for example. I thought the only way to guarantee that time was to use an atomic clock setting online ....

Any time-based security can be defeated by simply changing the clock of the host computer, whether it's an atomic clock or not.

I can see the physical security of the host computer being as important as the security in the database.