I am assuming <No Access> appears on the layout. If so, a grey box hides the information to which access is forbidden. Where this grey box appears determines what access is forbidden. If the entire layout is greyed out, that means layout access is forbidden. If the field is greyed out, that means field access or record access is forbidden.
If the latter is the case, remember that even if a user has access to view a record, the user may not have access to view a field.
You can also use the functions Get (LayoutAccess), Get (PrivilegeSetName), Get (RecordAccess) in the Data Viewer to find out what the access levels are while logged in as a problematic user.
Thanks for your reply.
I will have a look at my Database to see if this is the case. I'll let you know as soon as possible.
Thanks again for your response, its greatly appreciated.
I've had a look at my sample database and it seems to be in Browse Mode and not in layout (or am I confusing myself?)
I took a few screen shots to show what I'm getting or what my settings are:
When I log into any other account, with standard privileges (ie: Full Access, Data Entry Only Access or Read Only Access) the script takes me to the designated layout BUT when I select this particular usename (with create/edit records only and no delete) I get this <No Access> error messag.
Any other suggestions?
Furthermore, I'm not too clued up on scripts so can you please suggest how I can use the functions Get (LayoutAccess), Get (PrivilegeSetName), Get (RecordAccess) in the Data Viewer to find out what the access levels are while logged in as a problematic user?
In your priviledge settings you have layouts set to "No Access" so your end user cannot access any of your layouts, change the layout priviledge to "view only" for your end users.
I second SaterInc's assessment. I will add that you might want to give read access to the value lists too, as they are likely used during data entry.
I would like to thank both David and SaterInc for their excellent advice.
My immediate problem has been solved.
A BIG THANK YOU
Keep up the good work guys, we need people like you to help us novices develop.
Come to think of it, it was a silly mistake - I should have realised what I've done wrong BUT sometimes you can miss the obvious when it is stairing you right in the face (we're only human)