Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

Privileges / Restrict access to found records


This topic is 5475 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies
Posted

Hello

This is my first post as I'm really stuck this time - although I've found loads of useful advice here in the last year!

I've got a relatively complex DB but am self-taught so I'm sure it doesn't follow 'normal' design procedure!

Basically, I want to restrict access to certain found sets of data based on users privilege set - which I know how to test and have a startup script that gets this data into variables.

My problem is if I do 'find' script steps - it gives the correct data, but still leaves the user the option to 'show all' which I don;t want. If i restrict the interface, it also takes away too much other functionality. They access through IWP and FMnet so same thing with the web interface - it also has 'show all'.

I assume this can be done in relational links, but I'm confused - nothing I've tried works, and it seems like I then have to make a completely new set of layouts per privilege set - just so it points to the right tables?

Am I better off trying to sort out the interfaces, or restricting the data more securely?

Thanks for any help (and understanding!)

Posted

You might want to hide the status area from the users and recreate its functionality with customized buttons and calculated fields. For your example, you'd want a button that goes into find mode and adds the Users name to the find request so they only end up seeing records to which they have access.

This topic is 5475 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.