Help

[Goran]

There is the question:

I have established a cost
control system in Store Development using access.

Essentially I have two .mdb's, one is a back end
containing data
("STOREDEV_BE.mdb") , (not expected to be accessed
directly by users) and
the other is a front end linked to the back end tables,
accessible to users
("STOREDEV.mdb") . The properties of the file in Netware
are sharable,
transactional, archive, NOT read-only.

I want to provide security on the front end file, and
have established an
mdw file ("STOREDEV.mdw") , located in the same LAN
directory as the mdb's,
using the Access wizard. This works fine for me (I am
using Access).

However, my users are using Access Runtime, and using a
shortcut with the command
line :
S:\Storedev\_Database\STOREDEV.mdb /wrkgrp
S:
\Storedev\_Database\STOREDEV.mdw
they receive an error message
"You do not have the necessary permissions to
use the 'S:
\storedev\_database\STOREDEV.mdb' object".

I have tried setting up users within the .mdw with the
same names as their
ID on the LAN, and it doesn't make any difference;

Can you discuss / throw any light on why users can't
access the mdb???

That's it.
Thanks a lot.
Goran

 

[Joan Wild]

There is the question:

I have established a cost
control system in Store Development using access.

Essentially I have two .mdb's, one is a back end
containing data
("STOREDEV_BE.mdb") , (not expected to be accessed
directly by users) and
the other is a front end linked to the back end tables,
accessible to users
("STOREDEV.mdb") . The properties of the file in Netware
are sharable,
transactional, archive, NOT read-only.

I want to provide security on the front end file, and
have established an
mdw file ("STOREDEV.mdw") , located in the same LAN
directory as the mdb's,
using the Access wizard. This works fine for me (I am
using Access).

It is not a good idea to name your mdw the same as the mdb. Both files need
to create a ldb file when in use. Just rename the mdw file.

However, my users are using Access Runtime, and using a
shortcut with the command
line :
S:\Storedev\_Database\STOREDEV.mdb /wrkgrp
S:
\Storedev\_Database\STOREDEV.mdw
they receive an error message
"You do not have the necessary permissions to
use the 'S:
\storedev\_database\STOREDEV.mdb' object".

When you use a shortcut that has a switch like /wrkgrp, you must provide the
path to msaccess.exe. Without that included, the switch is ignored and
Access will start using the default system.mdw workgroup - that fact that
you are getting an error, suggests that you secured it properly. One other
note, you can use UNC pathnames rather than relying on each computer having
S: mapped to the correct location. You shortcut should be

"path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw"

Also you should consider putting a copy of the frontend on each user's
computer, rather than having all of them accessing the same frontend on the
server.