Group:  Microsoft Access ยป microsoft.public.access.security
Thread: workgroup information file (WIF) problem

DotNetBag
.NET Development Newsgroups

HTVi
TV Discussion Newsgroups

Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Rising Antivirus 2006

workgroup information file (WIF) problem
chouetteray 07.07.2006 20:51:02
I created a database on my local drive and secured it using the wizard. I
then placed a copy/shortcut on a different drive. No one can open it but me.
They all get an error message that they don't have permission... How do I
change the current WIF to point to the new drive and not my local drive?
Thanks a million.
Re: workgroup information file (WIF) problem
"Joan Wild" <jwild[ at ]nospamtyenet.com> 07.07.2006 21:06:21

chouetteray wrote:
[Quoted Text]
> I created a database on my local drive and secured it using the
> wizard. I then placed a copy/shortcut on a different drive.

Copy/shortcut of what? Did you copy the WIF to a network location that all
users have permissions to? Did you copy the MDB to a network location that
all users have permissions to? Did you copy the shortcut the wizard created
to each user's PC?


>No one
> can open it but me. They all get an error message that they don't
> have permission... How do I change the current WIF to point to the
> new drive and not my local drive? Thanks a million.

Copying the shortcut to each user's PC will work, provided they have Access
installed in the same location as you do on your computer.

The shortcut should look like:
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure.mdw"

You can use UNC pathnames for the mdb and mdw
(\\server\share\ rather than some mapped drive letter).

If you get the above working, you should split the database and leave the
backend (tables/relationships) on the server. Give each user a copy of the
frontend (all other objects with linked tables pointing to the backend on
the server) on their PC. Then modify the "path to mdb" portion of the
shortcut to point to the local copy of the frontend.mdb.

When you split it, don't use the splitter wizard as that will result in an
unsecure backend mdb. Instead split it manually.


--
Joan Wild
Microsoft Access MVP


Re: workgroup information file (WIF) problem
Ian 09.07.2006 22:10:01
Hi Joan,

Can you point me to a reference which explains how to manually split a db. I
have used the wizard previously but didn't realise that a manual split
preserves back-end security.

Thanks very mcuh,
Ian.

"Joan Wild" wrote:

[Quoted Text]
>
> chouetteray wrote:
> > I created a database on my local drive and secured it using the
> > wizard. I then placed a copy/shortcut on a different drive.
>
> Copy/shortcut of what? Did you copy the WIF to a network location that all
> users have permissions to? Did you copy the MDB to a network location that
> all users have permissions to? Did you copy the shortcut the wizard created
> to each user's PC?
>
>
> >No one
> > can open it but me. They all get an error message that they don't
> > have permission... How do I change the current WIF to point to the
> > new drive and not my local drive? Thanks a million.
>
> Copying the shortcut to each user's PC will work, provided they have Access
> installed in the same location as you do on your computer.
>
> The shortcut should look like:
> "path to msaccess.exe" "path to mdb" /wrkgrp "path to secure.mdw"
>
> You can use UNC pathnames for the mdb and mdw
> (\\server\share\ rather than some mapped drive letter).
>
> If you get the above working, you should split the database and leave the
> backend (tables/relationships) on the server. Give each user a copy of the
> frontend (all other objects with linked tables pointing to the backend on
> the server) on their PC. Then modify the "path to mdb" portion of the
> shortcut to point to the local copy of the frontend.mdb.
>
> When you split it, don't use the splitter wizard as that will result in an
> unsecure backend mdb. Instead split it manually.
>
>
> --
> Joan Wild
> Microsoft Access MVP
>
>
>
Re: workgroup information file (WIF) problem
"Joan Wild" <jwild[ at ]nospamtyenet.com> 10.07.2006 13:24:12
http://www.jmwild.com/SplitSecure.htm

--
Joan Wild
Microsoft Access MVP

Ian wrote:
[Quoted Text]
> Hi Joan,
>
> Can you point me to a reference which explains how to manually split
> a db. I have used the wizard previously but didn't realise that a
> manual split preserves back-end security.
>
> Thanks very mcuh,
> Ian.
>
> "Joan Wild" wrote:
>
>>
>> chouetteray wrote:
>>> I created a database on my local drive and secured it using the
>>> wizard. I then placed a copy/shortcut on a different drive.
>>
>> Copy/shortcut of what? Did you copy the WIF to a network location
>> that all users have permissions to? Did you copy the MDB to a
>> network location that all users have permissions to? Did you copy
>> the shortcut the wizard created to each user's PC?
>>
>>
>>> No one
>>> can open it but me. They all get an error message that they don't
>>> have permission... How do I change the current WIF to point to the
>>> new drive and not my local drive? Thanks a million.
>>
>> Copying the shortcut to each user's PC will work, provided they have
>> Access installed in the same location as you do on your computer.
>>
>> The shortcut should look like:
>> "path to msaccess.exe" "path to mdb" /wrkgrp "path to secure.mdw"
>>
>> You can use UNC pathnames for the mdb and mdw
>> (\\server\share\ rather than some mapped drive letter).
>>
>> If you get the above working, you should split the database and
>> leave the backend (tables/relationships) on the server. Give each
>> user a copy of the frontend (all other objects with linked tables
>> pointing to the backend on the server) on their PC. Then modify the
>> "path to mdb" portion of the shortcut to point to the local copy of
>> the frontend.mdb.
>>
>> When you split it, don't use the splitter wizard as that will result
>> in an unsecure backend mdb. Instead split it manually.
>>
>>
>> --
>> Joan Wild
>> Microsoft Access MVP


Home | Search | Terms | Imprint | Contact
Newsgroups Reader - provided by WiredBox.Net