By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
457,911 Members | 1,195 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 457,911 IT Pros & Developers. It's quick & easy.

Splitting/MDE's/Security

P: n/a
Hi all.
I've been getting my head around user-level security, and pretty much have
the hang of how to give defined access to different users. However I
normally implement using and MDE for the FE,on a local machine and an MDB
for the backend on a server drive. I intend to have a local mdw file on the
local install directory, and use the command line parameters of the shortcut
to point the database file to this file, when starting up.

I want to keep my installations separate from other access databases on the
client's machines, that;s why i'm using the command line to link with the
mdw file.

There are two ways for me to create the backend file, either copy the full
file, and remove all except the tables, then remove all the tables in the
front end, and link them from he backend. Or , use the database splitter.

Couple of questions for someone with experience of this.
Which one is going to be best to maintain the security.
Can the back end inherit the security using the the splitter, even across
the Lan.
If not, then how do I get the backend to refer to the local mdw file, or
does this remain fixed for the access 'session'

Thanks in advance.

Gerry Abbott


--

Nov 13 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Still hoping that someone will answer my post.

I have looked at old threads and found a very userful one, which clarifies
where the MDW files should be placed in a multi-user environment, and it
touches on the need to assign permissions to the table links, of a linked
file. But my questions below remain unanswered.

http://groups.google.com/groups?hl=e...nbbsa03#link10


Gerry Abbott
"Gerry Abbott" <pl****@ask.ie> wrote in message
news:oI*******************@news.indigo.ie...
Hi all.
I've been getting my head around user-level security, and pretty much have
the hang of how to give defined access to different users. However I
normally implement using and MDE for the FE,on a local machine and an MDB
for the backend on a server drive. I intend to have a local mdw file on
the local install directory, and use the command line parameters of the
shortcut to point the database file to this file, when starting up.

I want to keep my installations separate from other access databases on
the client's machines, that;s why i'm using the command line to link with
the mdw file.

There are two ways for me to create the backend file, either copy the full
file, and remove all except the tables, then remove all the tables in the
front end, and link them from he backend. Or , use the database splitter.

Couple of questions for someone with experience of this.
Which one is going to be best to maintain the security.
Can the back end inherit the security using the the splitter, even across
the Lan.
If not, then how do I get the backend to refer to the local mdw file, or
does this remain fixed for the access 'session'

Thanks in advance.

Gerry Abbott


--

Nov 13 '05 #2

P: n/a
On Wed, 29 Sep 2004 20:05:55 +0100, "Gerry Abbott" <pl****@ask.ie>
wrote:
Hi all.
I've been getting my head around user-level security, and pretty much have
the hang of how to give defined access to different users. However I
normally implement using and MDE for the FE,on a local machine and an MDB
for the backend on a server drive. I intend to have a local mdw file on the
local install directory, and use the command line parameters of the shortcut
to point the database file to this file, when starting up.
A shared MDW is easier to maintain instead of a multitude of MDW's on
the local machines. (if that is what you meant...)

Using the shortcut to specify the MDW is the correct way to do it.

I want to keep my installations separate from other access databases on the
client's machines, that;s why i'm using the command line to link with the
mdw file.

There are two ways for me to create the backend file, either copy the full
file, and remove all except the tables, then remove all the tables in the
front end, and link them from he backend. Or , use the database splitter.

Couple of questions for someone with experience of this.
Which one is going to be best to maintain the security.
Do it manually.

Can the back end inherit the security using the the splitter, even across
the Lan.
LAN is irrelevant. Apparently the splitter fails to properly apply
security to the BE (no personal experience -- I always do it manually)
If not, then how do I get the backend to refer to the local mdw file, or
does this remain fixed for the access 'session'
Each Access session is controlled by an MDW. The backend will use the
accounts from whatever MDW was used to launch Access. Matters not
whether you open Access, then open the FE or open Access, then open
the BE. In both cases, the MDW that you used to launch Access controls
the permissions on the BE.

Check the paper on the website in my signature for additional
information.

Thanks in advance.

Gerry Abbott

**********************
ja**************@telusTELUS.net
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security
Nov 13 '05 #3

P: n/a
Thanks Jack,

Nice paper, great help.

Regards,
Gerry Abbott

"Jack MacDonald" <ja**************@telus.net> wrote in message
news:uv********************************@4ax.com...
On Wed, 29 Sep 2004 20:05:55 +0100, "Gerry Abbott" <pl****@ask.ie>
wrote:
Hi all.
I've been getting my head around user-level security, and pretty much have
the hang of how to give defined access to different users. However I
normally implement using and MDE for the FE,on a local machine and an MDB
for the backend on a server drive. I intend to have a local mdw file on
the
local install directory, and use the command line parameters of the
shortcut
to point the database file to this file, when starting up.


A shared MDW is easier to maintain instead of a multitude of MDW's on
the local machines. (if that is what you meant...)

Using the shortcut to specify the MDW is the correct way to do it.

I want to keep my installations separate from other access databases on
the
client's machines, that;s why i'm using the command line to link with the
mdw file.

There are two ways for me to create the backend file, either copy the full
file, and remove all except the tables, then remove all the tables in the
front end, and link them from he backend. Or , use the database splitter.

Couple of questions for someone with experience of this.
Which one is going to be best to maintain the security.


Do it manually.

Can the back end inherit the security using the the splitter, even across
the Lan.


LAN is irrelevant. Apparently the splitter fails to properly apply
security to the BE (no personal experience -- I always do it manually)
If not, then how do I get the backend to refer to the local mdw file, or
does this remain fixed for the access 'session'


Each Access session is controlled by an MDW. The backend will use the
accounts from whatever MDW was used to launch Access. Matters not
whether you open Access, then open the FE or open Access, then open
the BE. In both cases, the MDW that you used to launch Access controls
the permissions on the BE.

Check the paper on the website in my signature for additional
information.

Thanks in advance.

Gerry Abbott

**********************
ja**************@telusTELUS.net
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security

Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.