Limiting access to scripts

[Donnie]

I have a db that will let our Estimators create Misc Work Requests for our company. They all log in with a password and are assigned a group that will display their name when they create a new record.

I also have a few users that need to print reports for weekly meetings or for accounting purposes.

My basic users do not need access to these reports. I have a script that will print the weekly report, and also the log for accounting. I can make it where, based on Access, they get an "access denied" message when they click on the link, but I want them to get nothing when they click on the link. Is there a way to add this to the scripts I want blocked out of their use? Keep in mind that there are appx 30 users and groups created, so I thought about some sort of "If" stmt based on the group, but I didn't want a HUMONGOUS script for all of the users that can or cannot get into it.

Short of upgrading to version 7, is there a way to do this? I have the file if needed, but I'll appreciate any thoughts or ideas.

Thank you.

Donnie Mayes

[Donnie]

I have a db that will let our Estimators create Misc Work Requests for our company. They all log in with a password and are assigned a group that will display their name when they create a new record.

I also have a few users that need to print reports for weekly meetings or for accounting purposes.

My basic users do not need access to these reports. I have a script that will print the weekly report, and also the log for accounting. I can make it where, based on Access, they get an "access denied" message when they click on the link, but I want them to get nothing when they click on the link. Is there a way to add this to the scripts I want blocked out of their use? Keep in mind that there are appx 30 users and groups created, so I thought about some sort of "If" stmt based on the group, but I didn't want a HUMONGOUS script for all of the users that can or cannot get into it.

Short of upgrading to version 7, is there a way to do this? I have the file if needed, but I'll appreciate any thoughts or ideas.

Thank you.

Donnie Mayes

[Donnie]

I have a db that will let our Estimators create Misc Work Requests for our company. They all log in with a password and are assigned a group that will display their name when they create a new record.

I also have a few users that need to print reports for weekly meetings or for accounting purposes.

My basic users do not need access to these reports. I have a script that will print the weekly report, and also the log for accounting. I can make it where, based on Access, they get an "access denied" message when they click on the link, but I want them to get nothing when they click on the link. Is there a way to add this to the scripts I want blocked out of their use? Keep in mind that there are appx 30 users and groups created, so I thought about some sort of "If" stmt based on the group, but I didn't want a HUMONGOUS script for all of the users that can or cannot get into it.

Short of upgrading to version 7, is there a way to do this? I have the file if needed, but I'll appreciate any thoughts or ideas.

Thank you.

Donnie Mayes

[DykstrL]

A password can be assinged to more than one group. Take for example your master password. That password is a member of all groups.

You could create a new group called "Reports", or whatever you want. Then for each script/button that you want to restrict add this:

If(PatternCount(Status(CurrentGroups),"Reports") > 0

{Your script to run goes here}

Else

Halt Script

EndIf

...or... you could go the other way:

If(PatternCount(Status(CurrentGroups),"Reports") = 0

Halt Script

Else

{Your script to run goes here}

EndIf

[DykstrL]

A password can be assinged to more than one group. Take for example your master password. That password is a member of all groups.

You could create a new group called "Reports", or whatever you want. Then for each script/button that you want to restrict add this:

If(PatternCount(Status(CurrentGroups),"Reports") > 0

{Your script to run goes here}

Else

Halt Script

EndIf

...or... you could go the other way:

If(PatternCount(Status(CurrentGroups),"Reports") = 0

Halt Script

Else

{Your script to run goes here}

EndIf

[DykstrL]

A password can be assinged to more than one group. Take for example your master password. That password is a member of all groups.

You could create a new group called "Reports", or whatever you want. Then for each script/button that you want to restrict add this:

If(PatternCount(Status(CurrentGroups),"Reports") > 0

{Your script to run goes here}

Else

Halt Script

EndIf

...or... you could go the other way:

If(PatternCount(Status(CurrentGroups),"Reports") = 0

Halt Script

Else

{Your script to run goes here}

EndIf

[Donnie]

Thanks for the reply. My question on this is how will it recognize the "Estimator" when they click on the "Create New" link? Right now, based on their password and group match, it gets the Status(currentgroups) and returns the first initial/last name of that person.

Can this still be accomplished by your solution? I apologize for what is probably very basic questions, but this has to go online Monday and this is my last major hurdle to get over.

Thank you again!

Donnie

[Donnie]

Thanks for the reply. My question on this is how will it recognize the "Estimator" when they click on the "Create New" link? Right now, based on their password and group match, it gets the Status(currentgroups) and returns the first initial/last name of that person.

Can this still be accomplished by your solution? I apologize for what is probably very basic questions, but this has to go online Monday and this is my last major hurdle to get over.

Thank you again!

Donnie

[Donnie]

Thanks for the reply. My question on this is how will it recognize the "Estimator" when they click on the "Create New" link? Right now, based on their password and group match, it gets the Status(currentgroups) and returns the first initial/last name of that person.

Can this still be accomplished by your solution? I apologize for what is probably very basic questions, but this has to go online Monday and this is my last major hurdle to get over.

Thank you again!

Donnie

[DykstrL]

Status(CurrentGoups) should return whatever group or groups that particular password has been assigned to. If you have used the first initial and last name for group names, then that is what you will get.

Here's an exercise that may give you an idea what is happening:

Create a calculation field with Status(CurrentGroups) and the result as unstored and as text. Place the field on a new blank layout. Stretch the field several lines long. Then set your opener script to go to that layout.

Open the file using different passwords and see what displays in the field. Since you can't directly access what password was entered when a user opens a file, assigning the password to a group allows you an alternative.

[DykstrL]

Status(CurrentGoups) should return whatever group or groups that particular password has been assigned to. If you have used the first initial and last name for group names, then that is what you will get.

Here's an exercise that may give you an idea what is happening:

Create a calculation field with Status(CurrentGroups) and the result as unstored and as text. Place the field on a new blank layout. Stretch the field several lines long. Then set your opener script to go to that layout.

Open the file using different passwords and see what displays in the field. Since you can't directly access what password was entered when a user opens a file, assigning the password to a group allows you an alternative.

[DykstrL]

Status(CurrentGoups) should return whatever group or groups that particular password has been assigned to. If you have used the first initial and last name for group names, then that is what you will get.

Here's an exercise that may give you an idea what is happening:

Create a calculation field with Status(CurrentGroups) and the result as unstored and as text. Place the field on a new blank layout. Stretch the field several lines long. Then set your opener script to go to that layout.

Open the file using different passwords and see what displays in the field. Since you can't directly access what password was entered when a user opens a file, assigning the password to a group allows you an alternative.