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

Security on back-end Access 2002 database.

P: n/a
icb
Hi I have a front-end/back-end setup. The front-end utilises all
unbound forms populating the back-end via the code I have written. All
fine so far.

Prior to splitting the database I ran the security wizard and used a
shortcut from the desktop. All fine except of course I can open the
back-end directly. The security FAQ appears to be out of date insofar
as there is no wrkgadm.exe with 2002 and therefore you simply run the
security wizard without having to go through the steps you had to in
previous versions (much better!)

I have tried to run the wizard on the back-end thinking I could 'join'
the previously created .MDW for the front-end. The wizard won't allow
that so I created a new one but then I cannot see any data in the
front-end. I suppose I could join directly but that is not ideal as
any database I open from the same location as the back-end will
require a logon. Any ideas?

Thanks
Paul
Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
ia**@mailblocks.com (icb) wrote:
Hi I have a front-end/back-end setup. The front-end utilises all
unbound forms populating the back-end via the code I have written. All
fine so far.

Prior to splitting the database I ran the security wizard and used a
shortcut from the desktop. All fine except of course I can open the
back-end directly. The security FAQ appears to be out of date insofar
as there is no wrkgadm.exe with 2002 and therefore you simply run the
security wizard without having to go through the steps you had to in
previous versions (much better!)

I have tried to run the wizard on the back-end thinking I could 'join'
the previously created .MDW for the front-end. The wizard won't allow
that so I created a new one but then I cannot see any data in the
front-end. I suppose I could join directly but that is not ideal as
any database I open from the same location as the back-end will
require a logon. Any ideas?

Thanks
Paul


Hi Paul.

I've never used A2002 (still on A97 & 2k) but my guess is that what you
need to do is open your FE (join the workgroup) then create a new blank
database from File ... New to import your BE objects into.

Very surprised to read your comment about there being no workgroup
administrator. There must be one somewhere! I'm on my A97 PC at the moment
so can't check, but I seem to remember that the A2k variant is called
something other than wrkgadm.exe.

HTH - Keith.
www.keithwilby.org.uk
Nov 12 '05 #2

P: n/a
"icb" <ia**@mailblocks.com> wrote in message
news:d5**************************@posting.google.c om...
Hi I have a front-end/back-end setup. The front-end utilises all
unbound forms populating the back-end via the code I have written. All
fine so far.

Prior to splitting the database I ran the security wizard and used a
shortcut from the desktop. All fine except of course I can open the
back-end directly. The security FAQ appears to be out of date insofar
as there is no wrkgadm.exe with 2002 and therefore you simply run the
security wizard without having to go through the steps you had to in
previous versions (much better!)

I have tried to run the wizard on the back-end thinking I could 'join'
the previously created .MDW for the front-end. The wizard won't allow
that so I created a new one but then I cannot see any data in the
front-end. I suppose I could join directly but that is not ideal as
any database I open from the same location as the back-end will
require a logon. Any ideas?

Thanks
Paul

In Access XP they moved the workgroup administrator so that it is now
accessible from within Access Tools>Security>Workgroup Administrator, which
I think was quite a sensible thing to do.

I would be slightly cautious about using the security wizard, unless you are
sure you could do everything without it if necessary (and then you might not
need it). Anyway, from memory, I believe this is what you would have to do:

As a member of the standard system.mdw workgroup, run the security wizard
for the back end, creating a new mdw. When you have finished this, join
this new mdw, open the front end and run the wizard again. This will let
you modify the workgroup information so you secure both halves with the same
mdw. When you are finished, go back and re-join the standard workgroup and
use a shortcut to start open the database with the new mdw.

Fletcher

Nov 12 '05 #3

P: n/a
icb
"Fletcher Arnold" <fl****@home.com> wrote in message news:<bv*********@titan.btinternet.com>...
"icb" <ia**@mailblocks.com> wrote in message
news:d5**************************@posting.google.c om...
Hi I have a front-end/back-end setup. The front-end utilises all
unbound forms populating the back-end via the code I have written. All
fine so far.

Prior to splitting the database I ran the security wizard and used a
shortcut from the desktop. All fine except of course I can open the
back-end directly. The security FAQ appears to be out of date insofar
as there is no wrkgadm.exe with 2002 and therefore you simply run the
security wizard without having to go through the steps you had to in
previous versions (much better!)

I have tried to run the wizard on the back-end thinking I could 'join'
the previously created .MDW for the front-end. The wizard won't allow
that so I created a new one but then I cannot see any data in the
front-end. I suppose I could join directly but that is not ideal as
any database I open from the same location as the back-end will
require a logon. Any ideas?

Thanks
Paul

In Access XP they moved the workgroup administrator so that it is now
accessible from within Access Tools>Security>Workgroup Administrator, which
I think was quite a sensible thing to do.

I would be slightly cautious about using the security wizard, unless you are
sure you could do everything without it if necessary (and then you might not
need it). Anyway, from memory, I believe this is what you would have to do:

As a member of the standard system.mdw workgroup, run the security wizard
for the back end, creating a new mdw. When you have finished this, join
this new mdw, open the front end and run the wizard again. This will let
you modify the workgroup information so you secure both halves with the same
mdw. When you are finished, go back and re-join the standard workgroup and
use a shortcut to start open the database with the new mdw.

Fletcher


Thanks for the advice - it worked!

wrkgadm.exe doesn't ship with Windows XP and as you said is part of
Access now. I have always used the 'manual' method of setting up
security but I found that with this method in Access 2002 I could
still open the database directly from explorer. I tried the wizard and
it worked fine but still had the problem as discussed above.

Anyhow it works and I now understand the logic. I can open the front
end directly but not the back end. When I try to open a linked table
in the front end I do not have permissions - perfect. Now to set up
permissions for users.

Once again thanks and a lot more straightforward than Microsoft's own
explanation on MSDN:

http://msdn.microsoft.com/library/de...ndsolution.asp

Paul
Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.