Re: Microsoft Access Security Best Practices when linking to a SQL back end
tdmailbox_at_yahoo.com
Date: 02/09/05
- Next message: cwatters: "Re: Distributing security in Access 2002"
- Previous message: Lynn Trapp: "Re: Microsoft Access Security Best Practices when linking to a SQL back end"
- In reply to: Lynn Trapp: "Re: Microsoft Access Security Best Practices when linking to a SQL back end"
- Next in thread: Paul Overway: "Re: Microsoft Access Security Best Practices when linking to a SQL back end"
- Reply: Paul Overway: "Re: Microsoft Access Security Best Practices when linking to a SQL back end"
- Messages sorted by: [ date ] [ thread ]
Date: 9 Feb 2005 12:55:19 -0800
Yes we would be keeping the access front end. So the access database
would open a security table on the sql backend from an access startup
form and use that to permission everyone. It would have to do exactly
what you said, check creditials and then close out access if they
provide bad credentials.
My biggest concern is actually what you said, trying to re-invent the
wheel by creating my own security algoritrhm and then in turn doing a
better job then the group of microsoft programs that designed the .mdw
security controls.
It isnt my IT staff that is pushing this, I am doing this application
for a client and it is their internal IT staff that was the one that
stated using a .mdw file would violate their security policy.
- Next message: cwatters: "Re: Distributing security in Access 2002"
- Previous message: Lynn Trapp: "Re: Microsoft Access Security Best Practices when linking to a SQL back end"
- In reply to: Lynn Trapp: "Re: Microsoft Access Security Best Practices when linking to a SQL back end"
- Next in thread: Paul Overway: "Re: Microsoft Access Security Best Practices when linking to a SQL back end"
- Reply: Paul Overway: "Re: Microsoft Access Security Best Practices when linking to a SQL back end"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
