Steve N Posted December 27, 2002 Posted December 27, 2002 I have created a time clock program with 2 files, time card and time card line items. I want to limit users to creating but not changing times. When I set up a password and unclick edit records, I can still edit with that password. What am I doing wrong. I also limited access to layouts with user passwords, but then my scripts don't work since the script goes to specified layout to perfrom its job. any work arounds
jasonwood Posted December 27, 2002 Posted December 27, 2002 my scripts don't work since the script goes to specified layout to perfrom its job Why would a script need to go to a layout to "perform it's job"? You aren't using "Instert Text" or similar script steps are you? You should be using "Set Field". As far as the access priveledges are concerned, if you have it set up so that a user can create but not modify a record, then I believe as soon as they exit the record, they can no longer make modifications. Simply include an "exit record" step in your script.
Steve N Posted January 3, 2003 Author Posted January 3, 2003 Thanks for such a quick reply. I do use set field where possible, however I use copy and paste to create a new related record in the line items. To make the clock in process easier for the user I have a clock in and clock out botton on the user screen. (the buttons are not in the portal) The only way I can create a related record is to copy employee in name, go to a subscript in line items, create and new record then paste employee name. I am working a way around. ON the access issue, I set up the line items with no edit privlages with the user password, but I can change any record with the user password. It seems like no edit would mean I could not change any record at any time. Steve
jasonwood Posted January 3, 2003 Posted January 3, 2003 Not sure about that "No Edit" problem, but as far as the field data is concerned, there is rarely a need to use copy/paste. To create a related record from a script you would set a global field to the key you wish to use, then run a subscript. The subscript looks back to the original database into that global field to get the data (using set field). It does not matter if there are presently related records, the global fields can still be reached through the relationship.
Recommended Posts
This topic is 7993 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 accountSign in
Already have an account? Sign in here.
Sign In Now