write create microsoft access rights?

B

BruceM

No. No need to continue. You can go away now.

message
yah..

NTFS ReadPerms for FrontEnd
NTFS ReadPerms for BackEnd
NTFS ReadPerms for TempDbEnd

NTFS WritePerms for FrontEnd
NTFS WritePerms for BackEnd
NTFS WritePerms for TempDbEnd

NTFS ExecutePerms for FrontEnd
NTFS ExecutePerms for BackEnd
NTFS ExecutePerms for TempDbEnd

NTFS DeletePerms for FrontEnd
NTFS DeletePerms for BackEnd
NTFS DeletePerms for TempDbEnd

JET Workgroup ReadPerms for FrontEnd
JET Workgroup ReadPerms for BackEnd
JET Workgroup ReadPerms for TempDbEnd

JET Workgroup WritePerms for FrontEnd
JET Workgroup WritePerms for BackEnd
JET Workgroup WritePerms for TempDbEnd

JET Workgroup FormPerms for FrontEnd
JET Workgroup QueryPerms for FrontEnd
JET Workgroup ReportPerms for FrontEnd


I mean.. do I really need to continue?

-Aaron
 
L

Larry Linson

Oh, do you have to keep quoting Mr. Kempf? Or am I going to have to change
my message rules to look in the body of the post, now?

That looks like three sets of permissions, except there's no need for one of
them ("temp DB"), though, not twelve. And, of course, whatever front end you
use you will have to have permissions and security on server databases is
usually even more complex than OS and Access security -- even if it is web
app it will need some permissions set in the browser.

Sounds like another "much ado about nothing" to me.

Larry Linson
Microsoft Office Access MVP
 
G

George

LOL, thanks. THAT was funny.


BruceM said:
No. No need to continue. You can go away now.

in message
yah..

NTFS ReadPerms for FrontEnd
NTFS ReadPerms for BackEnd
NTFS ReadPerms for TempDbEnd

NTFS WritePerms for FrontEnd
NTFS WritePerms for BackEnd
NTFS WritePerms for TempDbEnd

NTFS ExecutePerms for FrontEnd
NTFS ExecutePerms for BackEnd
NTFS ExecutePerms for TempDbEnd

NTFS DeletePerms for FrontEnd
NTFS DeletePerms for BackEnd
NTFS DeletePerms for TempDbEnd

JET Workgroup ReadPerms for FrontEnd
JET Workgroup ReadPerms for BackEnd
JET Workgroup ReadPerms for TempDbEnd

JET Workgroup WritePerms for FrontEnd
JET Workgroup WritePerms for BackEnd
JET Workgroup WritePerms for TempDbEnd

JET Workgroup FormPerms for FrontEnd
JET Workgroup QueryPerms for FrontEnd
JET Workgroup ReportPerms for FrontEnd


I mean.. do I really need to continue?

-Aaron
 
G

George Hepworth

Interesting. You stated, and I quote, "SQL Server allows you to set
permissions in just ONE place..
instead of in 12 different places."

You responded with a list of 18 different TYPES of permissions (NTFS
ReadPerms for FrontEnd, etc.) , not 12 places where you are allowed to set
permissions.

Again, focus and clarity are critical to being able to communicate your
points effectively. And that was my point in asking you to enumerate.

Also, given your response (listing types of permissions instead of places in
which one is allowed to set permissions), and the fact that you claim SQL
Server allows you to set permissions in just ONE place, the implication
would seem to be that you think there is ONE, and ONLY ONE, such type of
permission that can be set in SQL Server? Is that REALLY a good thing?

Let's assume, for the moment, that being able to set permissions in 12, or
18, or more, places is a bad thing. Is that because it allows the developer
to fine-tune different types of permissions across a lot objects in the
database and that developers shouldn't have that range of control?

Is the correllary also true then? It is a good thing that SQL Server limits
the developers ability to fine-tune permissions in the same sense, toa
single place, and that that lack of control is better?
 
S

So Sorry For Poor Aaron

a a r o n . k e m p f @ g m a i l . c o said:
Access 'saved queries' can _NOT_ be shared between users.
Two different people can not write queries at the same time
and share them.

Why, yes, when you add the additional qualifications, you are correct -- but
neither can SQL Server... both must be saved to be accessible and usable by
other users.
Anything else sounds like a PITA to me.

Oh, you just pointed out how SQL Server and Access (Jet/ACE) are alike -- so
you think SQL Server is a PITA? You surely back yourself into a lot of
corners, kid.
I know plenty more about SQL Server than anyone else on this group.

Claiming doesn't make it so. Your erroneous statements prove that it is NOT
so. We would probably be more inclined to believe a claim that you are an
expert in particle physics, because you haven't shown here that you are
ignorant about that subject, as you have shown about SQL Server.
and for the most part I'm probably better with Access
than 99.999 % people around here.

And, no one here believes that claim, because you have demonstrated that not
only are you more often wrong that right about that, but vastly more often
wrong than right. No one here believes, and their belief is justifiable, that
you are even basically competent in Access -- because you scan the Help,
misread and misinterpret what you read (because you don't know jack about it)
and try to use that to justify your recommendations of SQL Server, whether
they are justified or not, as they usually are not.
Just because I'm unpopular around here-- that
doesn't mean that I'm wrong.

No, kid, it is because you are so often (almost always) wrong, and haven't
the sense to know it, or the courage to admit it, that you are unpopular.
It just means that the database retards can't
get their way any longer.

I think this and your acknowlegement that queries must be saved both in SQL
Server and Access to be used by another user are the only true statements in
your post. You are the only Database Retard currently posting in this
newsgroup.
Some dipshit MVP said THREE incorrect things in a single post.

You aren't fit to clean the shoes of the MVPs who post here, nor of the MVPs
in the SQL Server newsgroups, where you are no more welcome. There's often
not even a single correct statement in your posts.
I'll gladly reccomend SQL Server where I see fit.

You ALWAYS see fit to recommend SQL Server. In this newsgroup, your
recommendations are almost never actually fit.
SQL Server slaughters Access in every category -- _ESPECIALLY_ price
and ease of development.

Don't you get tired of carrying around loads of manure as big as this one?
SQL Server, with the features you often recommend, it not free -- SQL Server
Express edition lacks many features you tell people they need. It requires
installation, it requires more training/knowledge to set up a database, and
except for the quite limited Express Edition, not only is expensive, but has
a per-seat charge for each user (also known as a Client Access License, or
CAL). But I suppose you don't have any idea what it costs. Even if a user
develops the client app in Access -- using ADPs, as you always suggest, costs
more time and effort than the MDBs you denigrate, but even MDBs are somewhat
more difficult when using SQL Server as a datastore.
If anyone else tries to tell you otherwise.. they are trying to sell
you some worthless obsolete JET crap.

If Aaron suggests SQL Server in this newsgroup, he is 99.999% of the time
trying to sell you something you don't need, that will cost you a lot of
money, and that will make your small-project development much more difficult.

By the way, Aaron, I hear all the Big brothers, Big Bubba, Big Butch, Big
Bruce, and Big Barney are all really eager for you to be issued another
orange jumpsuit and brought back to their cell block. They aren't in the
market for a database of any kind, so it doesn't make any difference to them
whether you know jack about SQL Server or Access (Jet or ACE). Keep up the
way you are going here, and they will soon have you back and they will be
happy. Keep practicing your lap dances.

So Sorry For Poor Aaron
 
A

a a r o n . k e m p f

Whatever, kid.

I'd much rather set _SECURE_ permissions in one place.. instead of
crappy permissions in twelve places.

-Aaron
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top