Re: Access 2010 article
- From: "David W. Fenton" <XXXusenet@xxxxxxxxxxxxxxxxxxx>
- Date: 8 Nov 2009 00:00:11 GMT
"Albert D. Kallal" <PleaseNOOOsPAMmkallal@xxxxxxx> wrote in
news:ETgJm.2403$rE5.1167@xxxxxxxxxxxx:
[re: security]
the
short answer is you have the full SharePoint security model here.
That security solves a TON of issues in terms of user Management.
You can certainly set user permissions on tables (SharePoint lists
- that means read, write, view, update etc). You can also of
course filter your web queries based on the user name. So, there
is a decent number of ways to manage these issues.
How does this integrate with client-side security? I guess this is
ACCDB-only functionality, which means you don't have Jet ULS, but,
well, what *do* you have?
That's a real puzzler for me, actually.
It seems to me that Sharepoint adds more security/user role
management than you get with Access using ACCDB, and that bugs me a
helluva lot. It seems like a way to kill the ACE, since to architect
a real app, why not just skip ACCDB and use the Sharepoint data
store for your desktop app?
Am I missing something here?
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.
- Follow-Ups:
- Re: Access 2010 article
- From: Albert D. Kallal
- Re: Access 2010 article
- References:
- Access 2010 article
- From: Bob Alston
- Re: Access 2010 article
- From: Albert D. Kallal
- Re: Access 2010 article
- From: Bob Alston
- Re: Access 2010 article
- From: Albert D. Kallal
- Re: Access 2010 article
- From: Salad
- Re: Access 2010 article
- From: Albert D. Kallal
- Access 2010 article
- Prev by Date: Re: Access 2010 article
- Next by Date: Re: Access 2010 with Sharepoint 2010
- Previous by thread: Re: Access 2010 article
- Next by thread: Re: Access 2010 article
- Index(es):
Relevant Pages
|