Access 2002 Conflicting Access 97

[Campbellbrian]

I have a database that I thought had fairly tight security applied to
it. It's in Access97. I'm running it also on a couple of machines that
shipped with Access 2002. This is probably not a good idea, but to
avoid rewriting the application I put A97 on the new machines and
setup my usual wrkgadm.exe to the .mdw that everyone else was using.
However when a user opens Access 2002 it wipes out the directive to
the .mdw and they can then open the 97 application with no security
prompts.
Any ideas?
Thanks! Brian

[Tom van Stiphout]

On 29 Sep 2003 14:16:17 -0700, ca************* **@yahoo.com
(Campbellbrian) wrote:

Don't change the default workgroup file. That's rude anyway.
Rather, use a shortcut to run your app:
<path to>msaccess.exe <path to>myprogram.md b /wrkgrp <path to my mdw>

-Tom.

I have a database that I thought had fairly tight security applied to
it. It's in Access97. I'm running it also on a couple of machines that
shipped with Access 2002. This is probably not a good idea, but to
avoid rewriting the application I put A97 on the new machines and
setup my usual wrkgadm.exe to the .mdw that everyone else was using.
However when a user opens Access 2002 it wipes out the directive to
the .mdw and they can then open the 97 application with no security
prompts.
Any ideas?
Thanks! Brian

[Albert D. Kallal]

First, if your users can create their own security file, or use a different
security file and then get into your palpations, then you don't have any
security at all do you?

If you have implemented security correctly, then the users will NOT be able
to get into the file unless they use YOUR security file. In fact, even if
your users where to create their own workgroup file, and add some users THEY
STILL CAN NOT GET into your file. If your users by accidentally using a
different workgroup file can get into your application then you HAVE NOT set
security correctly. If you have security set correctly, and you loose your
workgroup file, you CAN NOT get into the application. Something is wrong,a
and you have not implement security correctly.

Now, assuming you eventuality fix the above, then next problem is to fix the
security workgroup file setting when running a97, and running a2002. You
should ALWAYS give the users a short cut with the workgroup file set for
your database. (as mentioned, if they don't use your workgroup file, they
SHOULD be locked out. (since this is NOT the case, you as mentioned DO NOT
have security implement correctly).

At any rate, the advantage of setting the workgroup file in the shortcut is
that other access applications thus don't have to use, or even care about
YOUR workgroup file (you don't even have to bother setting, or joining the
workgroup file if you specify the workgroup file in your shortcut. And, as
mentioned, if they try and launch the mde file directly, they will NOT be
able to run it (thus, they will quickly learn they must use the shortcut
your provide). You can specify what workgroup file is to be used the in the
shortcut. It will look like:

"C:\Program Files\Microsoft Office\Office\m saccess.exe"
"c:\program files\Rides\Rid es.mdb"
/wrkgrp "c:\Program Files\Rides\Rid es.mdw"

You also need to download the security faq, and figure out what step you
missed, but for sure if users can get into your application with a different
workgroup file, then you don't have any security at all do you? When
security is setup correctly, you MUST use the correct workgroup file, or all
users will be locked out. And, as mentioned, even if a user creates THEIR
OWN new workgroup file, they STILL CAN NOT get in.

so, check out the security faq:

http://support.microsoft.com/default.aspx?scid=kb;[LN];207793
--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
ka****@msn.com
http://www.attcanada.net/~kallal.msn

[Terry Kreft]

You do not have a secured application if users can get into it using a
different workgroup file.

First get the Access Security White paper and apply it to your application
so that it is really secure.
Second use the command line which runs your app to point to the correct
workgroup file.

Terry
"Campbellbr ian" <ca************ ***@yahoo.com> wrote in message
news:e3******** *************** ***@posting.goo gle.com...

I have a database that I thought had fairly tight security applied to
it. It's in Access97. I'm running it also on a couple of machines that
shipped with Access 2002. This is probably not a good idea, but to
avoid rewriting the application I put A97 on the new machines and
setup my usual wrkgadm.exe to the .mdw that everyone else was using.
However when a user opens Access 2002 it wipes out the directive to
the .mdw and they can then open the 97 application with no security
prompts.
Any ideas?
Thanks! Brian

[TR]

To add to what the others have said, you almost certainly have not
implemented security properly. The two most obvious oversights are:
You have not removed all permissions from the default Users group.
You have not passworded the default admin user in your workgroup.
You have not removed the admin user from the admins group.

Ok, that was three oversights.
"Campbellbr ian" <ca************ ***@yahoo.com> wrote in message
news:e3******** *************** ***@posting.goo gle.com...

I have a database that I thought had fairly tight security applied to
it. It's in Access97. I'm running it also on a couple of machines that
shipped with Access 2002. This is probably not a good idea, but to
avoid rewriting the application I put A97 on the new machines and
setup my usual wrkgadm.exe to the .mdw that everyone else was using.
However when a user opens Access 2002 it wipes out the directive to
the .mdw and they can then open the 97 application with no security
prompts.
Any ideas?
Thanks! Brian

[Terry Kreft]

I think there's a law that you're allowed one oversight when pointing out
other peoples oversights.<g>.

Terry
"TR" <tr************ @mindREMOVEspri ng.com> wrote in message
news:BK******** ********@newsre ad2.news.atl.ea rthlink.net...

To add to what the others have said, you almost certainly have not
implemented security properly. The two most obvious oversights are:
You have not removed all permissions from the default Users group.
You have not passworded the default admin user in your workgroup.
You have not removed the admin user from the admins group.

Ok, that was three oversights.
"Campbellbr ian" <ca************ ***@yahoo.com> wrote in message
news:e3******** *************** ***@posting.goo gle.com...

I have a database that I thought had fairly tight security applied to
it. It's in Access97. I'm running it also on a couple of machines that
shipped with Access 2002. This is probably not a good idea, but to
avoid rewriting the application I put A97 on the new machines and
setup my usual wrkgadm.exe to the .mdw that everyone else was using.
However when a user opens Access 2002 it wipes out the directive to
the .mdw and they can then open the 97 application with no security
prompts.
Any ideas?
Thanks! Brian

[David W. Fenton]

te*********@mps .co.uk (Terry Kreft) wrote in
<bl**********@n ewsreaderm1.cor e.theplanet.net >:

I think there's a law that you're allowed one oversight when
pointing out other peoples oversights.<g>.

I think the law is that whenever you point out oversights by
someone else, you'll make one mistake yourself in the process.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Terry Kreft]

That's the one, hence my mistake.

Terry

"David W. Fenton" <dX********@bwa y.net.invalid> wrote in message
news:94******** *************** ****@24.168.128 .90...

te*********@mps .co.uk (Terry Kreft) wrote in
<bl**********@n ewsreaderm1.cor e.theplanet.net >:

I think there's a law that you're allowed one oversight when
pointing out other peoples oversights.<g>.

I think the law is that whenever you point out oversights by
someone else, you'll make one mistake yourself in the process.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc