Is there a way to prevent a user from clicking on a tab if every field associated with that tab is set to "No Access"? I dont want the users to see what fields are on that tab if they dont have access. Thanks!

Hi

try this one ...

The normal user can't see fields setted to "No Access"

ReservedTab.zip

Hi Daniele,

very nice trick, I always enjoy seeing your creativity !

Regards,

Peter

This is a brilliant solution to a problem I never knew I needed to solve, but it's driving me crazy. I can't work out how it works, nor can I replicate it.

OK the basic idea is to duplicate the table and relate the two tables together through a matched calculation field. The data in the matched field is determined by the login status of the user. Restricting the user privileges in relation to what may be accessed means that a non-Admin user doesn't get access to any fields based on the 2nd duplicate table.

But in my own database I can't get the fields to disappear completely. Also I have noticed that in the example, the fields behave differently depending on whether they are on the tabbed area or not. Why is this? Finally I notice that the labels disappear too. How come?

I'll keep working on this. I have a feeling I'm missing something very simple here. But I can't get it. Any tips would be appreciated.

Aliquis,

Indeed, you most definately are missing something. You have to look very close, but on the Admin tab, there is a one row portal that is basically the same size as the tab itself. The fields that you want to make disappear must reside in this portal. When the self join relationship is invalid, the portal will display nothing.

Ah .. many thanks. I did manage to work out that it was something to do with the tab control and I could see a shading when clicking it in browse mode, but I couldn't work out what it was. I was also wondering why a duplicate table needed to be set up, rather than just changing the privileges. But it's all now becoming clearer. Thanks again (and to raybaudi too)

OK got it now, but one further question. Is there a reason for changing the privileges and denying access to all 3 reserved fields? It seems to work well enough if you just deny user access for the 1 matching field. But maybe I'm missing something again.

Yes it may work with only restricting the one match field but to properly setup your security, you should not allow the privilege set 'User' to modify any of those fields as well.

Good point - thanks for your help on this.