SQL Server Access

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an MS Access project with SQL Server on the back end.

How do you suggest I develop access/security in this scenario? I have an
application with two types of Users. Those can Insert, Update or Select
from any table but thye may may not delete (Group A). Or those who can
Select on any table only (Group B).
What is the best way to implement this ? From what I have, defining User
Roles SQL server might work. If I I do that, how do I get access to work on
the right role for each type of user? (I could not find any Help on this in
SQL Server or the Access Project.)
 
In my 'Users' table I have different securities set up for each user. Then I
use a VBA solution in all my forms to check the table to see if that user can
Insert, Update, or just View the data. For instance, I have a form that has
an 'Add' button that is not enabled by default. I use VBA to query the
'Users' table to see if the user has rights to add a record associated with
that form. If the user can add a record I enable the button, if not, I leave
the button greyed (unenabled). I so the same thing with an 'Edit' button on
forms where users can edit a record.
Of course on the production versions users cannot get to the database window
so there is no chance they can get to a record except through a particular
form. This way I don't have to also set permissions in SQL server.

Hope this helps.
 
If your app, be it Access ADP or other type, access the SQL server database
in a fairly simple manner, then it may be OK to develop your own data access
security. But such a "re-inventing wheel" type of work can hardly be good
enough without invest significantly.

SQL Server itself provide powerful and flexible enough security mechanism.
I'd simply create appropriate SQL Server logins and uses/roles in the
database and give permission respectively.

Since OP uses ADP and it mostlikely is used in a LAN with each user has his
domain user account. iin this case, to use windows security on SQL Server is
very simple.
 
U¿ytkownik "Patrick said:
I have an MS Access project with SQL Server on the back end.

How do you suggest I develop access/security in this scenario? I have an
application with two types of Users. Those can Insert, Update or Select
from any table but thye may may not delete (Group A). Or those who can
Select on any table only (Group B).
What is the best way to implement this ? From what I have, defining User
Roles SQL server might work. If I I do that, how do I get access to work on
the right role for each type of user? (I could not find any Help on this in
SQL Server or the Access Project.)
Click to expand...
===========================================================================
FULL LEGAL SOFTWARE !!!
Games, video, program, image, chat, questbook, catalog site, arts, news,
and...
This site it is full register and legal software !!!
Please download and you must register software !!!

PLEASE REGISTER SOFTWARE:
http://www.webteam.gsi.pl/rejestracja.htm
DOWNLOAD LEGAL SOFTWARE:
http://www.webteam.gsi.pl

Full question and post: http://www.webteam.gsi.pl

Contact and service and advanced technology:
http://www.webteam.gsi.pl/kontakt.htm
FAQ: http://www.webteam.gsi.pl/naj_czesciej_zadawane_pytania.htm

Please add me URL for you all site and search engines and best friends !!!

Me site:
SERWIS WEBNETI: http://www.webneti.gsi.pl
PORTAL WEBTEAM:http://www.webteam.gsi.pl
LANGUAGE: http://www.webneti.cjb.net

==========================================================================
 
Hi,

No I don't sell it, just use it. I initially asked the newsgroup for ideas
but I instead found this product on a Google search. Anyway, works for me.

Let us know if you find something similar.
 
Anyway, works for me.
Click to expand...
Good for you.

Let us know if you find something similar.
Click to expand...
No thanks, I will not. Somehow it doesnt feel right to recommend a
commercial product in lieu of an answer to a specific technical question on
a non-commercial, voluntary newsgroup where people come to ask for help not
for product recommendation.

Let me know if you feel differently.


Regards,
Immanuel Sibero
 
Someone is a little short-sighted...

Just as someone has started this Post asking about SQL Server security I too
posed the same question to the same Group. The question was 'techincal'
because I did not know the best method to solve the security issue. It seemed
the only way to security tables was to use Stored Procedures, and this itself
was difficult to implement and maintain.

I followed up my Post asking if Microsoft had a tool that assisted
developers in this area. The reply by a MSDN developer was no, but that I
should add this as an improvement to Access .adp development.

From that experience I replied to this Post with a suggestive product, that
I am not affiliated with, to assist a member of this newsgroup with an issue.
When I asked for comments regarding an alternative way I did not suggest you
recommend another Product, but perhaps 'technical' instructions, say
regarding, Stored Procedure implementation for table security, or the like...

Your responses to my posting indicate that you are straying away from the
initial question Posted. Can you please be more helpful and provide
informative answers to a Post in the future, rather than slander a member for
their response.

Please do not respond to this Post instead assist Members, or better still,
email the Group administrator if you are not happy with my reponses.
 
I suspect it's not a case of "short-sighted" so much is it's probably just a
case of being fed up with spammers. While many people genuinely want to
recommend a product that they've used successfully, far too many simply
stand to benefit from some form of under-handed advertising.

I've seen other posts by you, so I can reasonably assume that your
intentions were perfectly benign...would that every other post was!

Anyway, don't take it too hard...everybody flies off the handle now & then.
:)



Rob
 
Back
Top