Allow access to enter data through forms, but not full database access
Using Access 2013 or Sharepoint 2013 is it possible to give someone access to data entry forms that work with a back-end database whether Access database or Sharepoint SQL.
But from everything I've looked at I can't find a way to separate someone from entering data and viewing all data?
For example in Access even if I split the database to a back end, it still has all the tables linked, and fully accessible from the "front end" this seems to be needed to allow Write access, it seems that you can have no access, read-only access and Read/Write access but no write-only access (this might be where I am wrong).
I don't want the people entering data to see the back end data (regardless if they are on Sharepoint or in access) and certainly do not want them to be able to modify the database directly (they should only be able to enter data via a form that can be validated before entered.)
Now I come from a Windows Forms and ASP.NET MVC background. I am used to hosting a SQL server and simply not writing code that pulls data from the database, and if I did I could set parameters on what data they could access. I could also set up server-side validation based on users and groups.
I can't seem to find any documentation on how to do this in either Access or on Sharepoint. I have read every article I could find on these topics via google and Support.Office.com for starters:
Introduction to integrating data between Access and a SharePoint site
Ways to share an Access desktop database
SharePoint Online environment
and a multitude of other articles both on TechNet and various third-party sites. While some do touch base on user access rights, they seem to allow only access to a specific site or database, not parts of, as my needs are allowed access to a way to enter data but not access to the data.
The client I am working with is addiment on using Access and Sharepoint. And before telling them I can't limit a user to data entry only, I wanted to check here first.
I did read a site that stated an issue with Access 2013 and Sharepoint is
Security setup is basic and somewhat limited. Item (or row) level security is not possible and edit access appears to allow users to edit information across all tables – not just one.
this was found here: http://blogs.perficient.com
but this seems to state that when you give someone table access they have all tables, and NOT that you can't restrict table access.
It does seem to state however that the only true options are HTML or developing something stand alone in Visual Studios.
database-design security ms-access users sharepoint
add a comment |
Using Access 2013 or Sharepoint 2013 is it possible to give someone access to data entry forms that work with a back-end database whether Access database or Sharepoint SQL.
But from everything I've looked at I can't find a way to separate someone from entering data and viewing all data?
For example in Access even if I split the database to a back end, it still has all the tables linked, and fully accessible from the "front end" this seems to be needed to allow Write access, it seems that you can have no access, read-only access and Read/Write access but no write-only access (this might be where I am wrong).
I don't want the people entering data to see the back end data (regardless if they are on Sharepoint or in access) and certainly do not want them to be able to modify the database directly (they should only be able to enter data via a form that can be validated before entered.)
Now I come from a Windows Forms and ASP.NET MVC background. I am used to hosting a SQL server and simply not writing code that pulls data from the database, and if I did I could set parameters on what data they could access. I could also set up server-side validation based on users and groups.
I can't seem to find any documentation on how to do this in either Access or on Sharepoint. I have read every article I could find on these topics via google and Support.Office.com for starters:
Introduction to integrating data between Access and a SharePoint site
Ways to share an Access desktop database
SharePoint Online environment
and a multitude of other articles both on TechNet and various third-party sites. While some do touch base on user access rights, they seem to allow only access to a specific site or database, not parts of, as my needs are allowed access to a way to enter data but not access to the data.
The client I am working with is addiment on using Access and Sharepoint. And before telling them I can't limit a user to data entry only, I wanted to check here first.
I did read a site that stated an issue with Access 2013 and Sharepoint is
Security setup is basic and somewhat limited. Item (or row) level security is not possible and edit access appears to allow users to edit information across all tables – not just one.
this was found here: http://blogs.perficient.com
but this seems to state that when you give someone table access they have all tables, and NOT that you can't restrict table access.
It does seem to state however that the only true options are HTML or developing something stand alone in Visual Studios.
database-design security ms-access users sharepoint
add a comment |
Using Access 2013 or Sharepoint 2013 is it possible to give someone access to data entry forms that work with a back-end database whether Access database or Sharepoint SQL.
But from everything I've looked at I can't find a way to separate someone from entering data and viewing all data?
For example in Access even if I split the database to a back end, it still has all the tables linked, and fully accessible from the "front end" this seems to be needed to allow Write access, it seems that you can have no access, read-only access and Read/Write access but no write-only access (this might be where I am wrong).
I don't want the people entering data to see the back end data (regardless if they are on Sharepoint or in access) and certainly do not want them to be able to modify the database directly (they should only be able to enter data via a form that can be validated before entered.)
Now I come from a Windows Forms and ASP.NET MVC background. I am used to hosting a SQL server and simply not writing code that pulls data from the database, and if I did I could set parameters on what data they could access. I could also set up server-side validation based on users and groups.
I can't seem to find any documentation on how to do this in either Access or on Sharepoint. I have read every article I could find on these topics via google and Support.Office.com for starters:
Introduction to integrating data between Access and a SharePoint site
Ways to share an Access desktop database
SharePoint Online environment
and a multitude of other articles both on TechNet and various third-party sites. While some do touch base on user access rights, they seem to allow only access to a specific site or database, not parts of, as my needs are allowed access to a way to enter data but not access to the data.
The client I am working with is addiment on using Access and Sharepoint. And before telling them I can't limit a user to data entry only, I wanted to check here first.
I did read a site that stated an issue with Access 2013 and Sharepoint is
Security setup is basic and somewhat limited. Item (or row) level security is not possible and edit access appears to allow users to edit information across all tables – not just one.
this was found here: http://blogs.perficient.com
but this seems to state that when you give someone table access they have all tables, and NOT that you can't restrict table access.
It does seem to state however that the only true options are HTML or developing something stand alone in Visual Studios.
database-design security ms-access users sharepoint
Using Access 2013 or Sharepoint 2013 is it possible to give someone access to data entry forms that work with a back-end database whether Access database or Sharepoint SQL.
But from everything I've looked at I can't find a way to separate someone from entering data and viewing all data?
For example in Access even if I split the database to a back end, it still has all the tables linked, and fully accessible from the "front end" this seems to be needed to allow Write access, it seems that you can have no access, read-only access and Read/Write access but no write-only access (this might be where I am wrong).
I don't want the people entering data to see the back end data (regardless if they are on Sharepoint or in access) and certainly do not want them to be able to modify the database directly (they should only be able to enter data via a form that can be validated before entered.)
Now I come from a Windows Forms and ASP.NET MVC background. I am used to hosting a SQL server and simply not writing code that pulls data from the database, and if I did I could set parameters on what data they could access. I could also set up server-side validation based on users and groups.
I can't seem to find any documentation on how to do this in either Access or on Sharepoint. I have read every article I could find on these topics via google and Support.Office.com for starters:
Introduction to integrating data between Access and a SharePoint site
Ways to share an Access desktop database
SharePoint Online environment
and a multitude of other articles both on TechNet and various third-party sites. While some do touch base on user access rights, they seem to allow only access to a specific site or database, not parts of, as my needs are allowed access to a way to enter data but not access to the data.
The client I am working with is addiment on using Access and Sharepoint. And before telling them I can't limit a user to data entry only, I wanted to check here first.
I did read a site that stated an issue with Access 2013 and Sharepoint is
Security setup is basic and somewhat limited. Item (or row) level security is not possible and edit access appears to allow users to edit information across all tables – not just one.
this was found here: http://blogs.perficient.com
but this seems to state that when you give someone table access they have all tables, and NOT that you can't restrict table access.
It does seem to state however that the only true options are HTML or developing something stand alone in Visual Studios.
database-design security ms-access users sharepoint
database-design security ms-access users sharepoint
edited 15 mins ago
Pang
1276
1276
asked Mar 11 '15 at 18:41
user2125348user2125348
11325
11325
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Use stored procedures, which can validate input before issuing the SQL commands. The user can be given rights to the stored procedure without any other access.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f95009%2fallow-access-to-enter-data-through-forms-but-not-full-database-access%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Use stored procedures, which can validate input before issuing the SQL commands. The user can be given rights to the stored procedure without any other access.
add a comment |
Use stored procedures, which can validate input before issuing the SQL commands. The user can be given rights to the stored procedure without any other access.
add a comment |
Use stored procedures, which can validate input before issuing the SQL commands. The user can be given rights to the stored procedure without any other access.
Use stored procedures, which can validate input before issuing the SQL commands. The user can be given rights to the stored procedure without any other access.
edited Jul 31 '15 at 0:35
answered Mar 12 '15 at 2:16
DemiDemi
1364
1364
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f95009%2fallow-access-to-enter-data-through-forms-but-not-full-database-access%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown