PC Review


Reply
Thread Tools Rate Thread

With and Without (not Pink Floyd)

 
 
=?Utf-8?B?RGF2ZQ==?=
Guest
Posts: n/a
 
      23rd Nov 2005
Hello,

I have an Access 2000 database running on WinXP that uses two shortcuts to
open the database. One shortcut is for the administrator that uses the MDW
file and prompts for the useid and password. The other shortcut is for
"regular" users that opens the MDB file without security. I want to split the
MDB into a FE/BE configuration and keep the same "simple" security setup. I
can lockdown the BE using a trick found in this discussion group. But, when I
try to use the "regular" shortcut to open the database, I get an Access
warning msgbox telling me I don't have permissions to the linked tables thru
the FE. Is there a way to keep the Admin/Regular shortcuts?

Thanks,

Dave
 
Reply With Quote
 
 
 
 
Keith W
Guest
Posts: n/a
 
      24th Nov 2005
"Dave" <(E-Mail Removed)> wrote in message
news:74067082-2BB0-4D18-9048-(E-Mail Removed)...
> Hello,
>
> I have an Access 2000 database running on WinXP that uses two shortcuts to
> open the database. One shortcut is for the administrator that uses the MDW
> file and prompts for the useid and password. The other shortcut is for
> "regular" users that opens the MDB file without security. I want to split
> the
> MDB into a FE/BE configuration and keep the same "simple" security setup.
> I
> can lockdown the BE using a trick found in this discussion group. But,
> when I
> try to use the "regular" shortcut to open the database, I get an Access
> warning msgbox telling me I don't have permissions to the linked tables
> thru
> the FE. Is there a way to keep the Admin/Regular shortcuts?
>


"And after all it's what the fighting's all about."

First off, all Access databases use an mdw file, by default this is
"system.mdw" located somewhere where you installed Office. By default,
"system.mdw" allows full permissions to all users for new databases and
existing ones that haven't been secured. You should not modify "system.mdw"
because it can prevent "ordinary" users from opening unsecured apps.

So your "regular" users are being authenticated against "system.mdw" and
allowed full access? Seems unlikely. Anyway, you need your front and back
ends to be affiliated with the same mdw file. Once you've secured one of
them, stay joined to your workgroup, close the mdb but keep the Access shell
open. Create a new blank database and import all of the objects from the
unsecured mdb into it. Re-link your tables as appropriate.

If you haven't read the MS FAQ on Access security then I recommend you do so
as it is essential reading. There's a link to it on my web site and there's
also a step-by-step example on there too which you might find useful.

HTH - Keith.
www.keithwilby.com


 
Reply With Quote
 
 
 
 
=?Utf-8?B?RGF2ZQ==?=
Guest
Posts: n/a
 
      28th Nov 2005
Thanks Keith. I hit the documentation.

Dave

"Keith W" wrote:

> "Dave" <(E-Mail Removed)> wrote in message
> news:74067082-2BB0-4D18-9048-(E-Mail Removed)...
> > Hello,
> >
> > I have an Access 2000 database running on WinXP that uses two shortcuts to
> > open the database. One shortcut is for the administrator that uses the MDW
> > file and prompts for the useid and password. The other shortcut is for
> > "regular" users that opens the MDB file without security. I want to split
> > the
> > MDB into a FE/BE configuration and keep the same "simple" security setup.
> > I
> > can lockdown the BE using a trick found in this discussion group. But,
> > when I
> > try to use the "regular" shortcut to open the database, I get an Access
> > warning msgbox telling me I don't have permissions to the linked tables
> > thru
> > the FE. Is there a way to keep the Admin/Regular shortcuts?
> >

>
> "And after all it's what the fighting's all about."
>
> First off, all Access databases use an mdw file, by default this is
> "system.mdw" located somewhere where you installed Office. By default,
> "system.mdw" allows full permissions to all users for new databases and
> existing ones that haven't been secured. You should not modify "system.mdw"
> because it can prevent "ordinary" users from opening unsecured apps.
>
> So your "regular" users are being authenticated against "system.mdw" and
> allowed full access? Seems unlikely. Anyway, you need your front and back
> ends to be affiliated with the same mdw file. Once you've secured one of
> them, stay joined to your workgroup, close the mdb but keep the Access shell
> open. Create a new blank database and import all of the objects from the
> unsecured mdb into it. Re-link your tables as appropriate.
>
> If you haven't read the MS FAQ on Access security then I recommend you do so
> as it is essential reading. There's a link to it on my web site and there's
> also a step-by-step example on there too which you might find useful.
>
> HTH - Keith.
> www.keithwilby.com
>
>
>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Re: pink elephants? A pink vista! Bill Yanaire Windows Vista General Discussion 1 28th Mar 2008 05:01 PM
Pink Pages, Pink Theme ! =?Utf-8?B?cGl4ZWxwdXA=?= Windows XP New Users 4 3rd Mar 2005 10:53 PM
pink blots and lines on the monitor (screen) =?Utf-8?B?VmFsYm9uYQ==?= Windows XP Performance 2 6th Jan 2005 05:32 PM
Black screen and pink/turquoise buttons. =?Utf-8?B?TWFyaW9fMjNfOTk=?= Windows XP General 1 28th Oct 2004 01:42 PM
Re: Flickering and pink screen Sharon F Windows XP Basics 0 23rd Feb 2004 05:36 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 05:37 PM.