Hi everyone,

I have been developing in FileMaker for a number of years (since v2.0). I am an in-house developer at a law firm.

Here is the problem. I have designed a database that keeps track of employee info. One of the fields is for salary. The firm does not want me to have access to the data in that field. I cannot think of a way to lock myself from a field and still be able to work as a designer on the system. Essentially, they do not want me to view any of the salary information that is to be entered in the system.

I've never had a situation like this to date. Can anyone suggest a way of doing this?

BTW, the solution is currently in v6 but I will be upgrading it to v8 in the next few months.

Regards,

Ken

I'm not 100% certain but I think that as the developer you will have 100% access and that's the way it is.

I once worked for a small company that was so concerned about salary information that the only person that the owner would allow to be the system administrator (non-Filemaker) was the accountant. The bad part is that the accountant had absolutely no interest in being the systems administrator and to no one's surprise, he was genuinely lousy at it. Of course everybody suffered because of it, even the business owner, but I'll have to admit that no salary information ever got out.

Perhaps create a related file--file not table--with appropriate field level restrictions to hold jsut the salary information. Include a reset password script. When finished with the file, have management run that script, change the password, and hope they don't forget it.

You'll need to test first extensively.

Steven

Ted and Steven, thank you both for your replies.

I will look into your suggestion Steven. That very well may work. I must admit, this is a rather awkward situation that I've never come across yet.

My only concern would be if I need to work on any of the salary functions, I would effectively be locked out. If it turns out to be a huge hassle, I may just suggest to management that they keep the salary information in a seperate system that I would not be involved with.

Best regards,

Ken