mde and user level security

N

naragus

I have a database application running on access97 and I need to run in on
several stations without installing office.
I thought conversion to mde and installing of AccessRuntime would do it. But,
my database uses user level security so users can´t open the mde file as
WRKGADM.EXE is not present on their system.
Any suggestion?
Thank you
 
B

Banana

I think I was one who suggested the possibility of securing a mde.

That said, it sounds like it may not be allowing the public role to the
mde, if that's what you were intending- allow anyone to run the MDE but
do not have the unlimited permissions as by default, yes?

If so, I would suggest reading this excellent resource:
http://www.geocities.com/jacksonmacd/AJMAccessSecurity.pdf

and also Security FAQ:
http://support.microsoft.com/kb/207793

Note especially #19, #21, and #26.

Hopefully this will help you work out the irons.
 
N

naragus via AccessMonster.com

Thank you for your information.
I read both articles but...........
If a workstation has no office(access) installed, how can the user provide
the "user/password" data when launching the .mde file with AccessRuntime? The
WRKGADM.EXE program is not present.

I think I was one who suggested the possibility of securing a mde.

That said, it sounds like it may not be allowing the public role to the
mde, if that's what you were intending- allow anyone to run the MDE but
do not have the unlimited permissions as by default, yes?

If so, I would suggest reading this excellent resource:
http://www.geocities.com/jacksonmacd/AJMAccessSecurity.pdf

and also Security FAQ:
http://support.microsoft.com/kb/207793

Note especially #19, #21, and #26.

Hopefully this will help you work out the irons.
I have a database application running on access97 and I need to run in on
several stations without installing office.
[quoted text clipped - 3 lines]
Any suggestion?
Thank you
 
B

Banana

The point is that you don't create a user and password for the end
users. You just allow the default "Admin" user to access all of the
database objects but with restricted permissions. You do not need to
distribute a .mdw or use workgroup administrator to join a different
workgroup.

As the article discussed, "Admin" user as well as the "Users" group is
identical in all workgroup security, even the default system.mdw. Your
goal is to grant the "Admin" user and "Users" limited permissions (e.g.
open certain forms, modify data, whatever is appropriate) while your
custom workgroup security takes the ownership of the databsae as well as
the objects (and the new objects too).

If you restrict all permissions from the Users group and Admin user then
you would need a password combination, but my suggestion was simply to
restrict the permission, rather than block out the Users group and Admin
user.

Did it help?
Thank you for your information.
I read both articles but...........
If a workstation has no office(access) installed, how can the user provide
the "user/password" data when launching the .mde file with AccessRuntime? The
WRKGADM.EXE program is not present.

I think I was one who suggested the possibility of securing a mde.

That said, it sounds like it may not be allowing the public role to the
mde, if that's what you were intending- allow anyone to run the MDE but
do not have the unlimited permissions as by default, yes?

If so, I would suggest reading this excellent resource:
http://www.geocities.com/jacksonmacd/AJMAccessSecurity.pdf

and also Security FAQ:
http://support.microsoft.com/kb/207793

Note especially #19, #21, and #26.

Hopefully this will help you work out the irons.
I have a database application running on access97 and I need to run in on
several stations without installing office.
[quoted text clipped - 3 lines]
Any suggestion?
Thank you
 
G

Graham Mandeno

Hi naragus

WRKADM.EXE is only used for creating workgroup files, and for setting the
*default* workgroup file on the local computer.

You should distribute your own workgroup file with your application, and
then explicitly specify the file on the command line of any shortcut that is
used to open the database.

For example, with the runtime installed in C:\MyApps\ART\, and the database
file C:\MyApps\MyDB.mde, and a workgroup file C:\MyApps\MyWorkgroup.mdw, the
command line would look like this:

"C:\MyApps\ART\msaccess.exe" /wrkgrp:"C:\MyApps\MyWorkgroup.mdw"
"C:\MyApps\MyDB.mde"

You would probably also add /user:someuser since Admin ought to have all
permissions disabled.
 
N

naragus via AccessMonster.com

Hi Graham
Thank you for your answer.
In your command line msaccess.exe is invoked, but the workstations don´t have
msaccess.
Is it possible to launch the mde application through AccessRuntime providing
user-password parameter in the command line?


Graham said:
Hi naragus

WRKADM.EXE is only used for creating workgroup files, and for setting the
*default* workgroup file on the local computer.

You should distribute your own workgroup file with your application, and
then explicitly specify the file on the command line of any shortcut that is
used to open the database.

For example, with the runtime installed in C:\MyApps\ART\, and the database
file C:\MyApps\MyDB.mde, and a workgroup file C:\MyApps\MyWorkgroup.mdw, the
command line would look like this:

"C:\MyApps\ART\msaccess.exe" /wrkgrp:"C:\MyApps\MyWorkgroup.mdw"
"C:\MyApps\MyDB.mde"

You would probably also add /user:someuser since Admin ought to have all
permissions disabled.
I have a database application running on access97 and I need to run in on
several stations without installing office.
[quoted text clipped - 4 lines]
Any suggestion?
Thank you
 
G

Graham Mandeno

Hi naragus

When you install the Access runtime, you install a version of msaccess.exe -
the run-time version.

In the command line I gave you, C:\MyApps\ART\ is the location where you
chose to install the run-time.

Sorry I didn't make that clear.

--
Good Luck :)

Graham Mandeno [Access MVP]
Auckland, New Zealand

naragus via AccessMonster.com said:
Hi Graham
Thank you for your answer.
In your command line msaccess.exe is invoked, but the workstations don´t
have
msaccess.
Is it possible to launch the mde application through AccessRuntime
providing
user-password parameter in the command line?


Graham said:
Hi naragus

WRKADM.EXE is only used for creating workgroup files, and for setting the
*default* workgroup file on the local computer.

You should distribute your own workgroup file with your application, and
then explicitly specify the file on the command line of any shortcut that
is
used to open the database.

For example, with the runtime installed in C:\MyApps\ART\, and the
database
file C:\MyApps\MyDB.mde, and a workgroup file C:\MyApps\MyWorkgroup.mdw,
the
command line would look like this:

"C:\MyApps\ART\msaccess.exe" /wrkgrp:"C:\MyApps\MyWorkgroup.mdw"
"C:\MyApps\MyDB.mde"

You would probably also add /user:someuser since Admin ought to have all
permissions disabled.
I have a database application running on access97 and I need to run in on
several stations without installing office.
[quoted text clipped - 4 lines]
Any suggestion?
Thank you
 
N

naragus via AccessMonster.com

Hi Graham,
Thank you again for your answer.
I´ve tried it and it works wonderfull.
In fact there is no need to include msaccess.exe in the command line.
It´s working with:
x:\123.mde /wrkgrp "x:\alfa.mdw"
bye bye.


Graham said:
Hi naragus

When you install the Access runtime, you install a version of msaccess.exe -
the run-time version.

In the command line I gave you, C:\MyApps\ART\ is the location where you
chose to install the run-time.

Sorry I didn't make that clear.
Hi Graham
Thank you for your answer.
[quoted text clipped - 32 lines]
 
J

Joan Wild

I don't believe this. Unless there's something peculiar about the
runtime, switches have always been ignored when msaccess.exe isn't
supplied. Can someone comment/verify?

If it's 'working' then it must/might be opening without using alfa.mdw
and therefore it's not secure at all.

Joan Wild

Hi Graham,
Thank you again for your answer.
I´ve tried it and it works wonderfull.
In fact there is no need to include msaccess.exe in the command line.
It´s working with:
x:\123.mde /wrkgrp "x:\alfa.mdw"
bye bye.


Graham said:
Hi naragus

When you install the Access runtime, you install a version of msaccess.exe -
the run-time version.

In the command line I gave you, C:\MyApps\ART\ is the location where you
chose to install the run-time.

Sorry I didn't make that clear.
Hi Graham
Thank you for your answer.
[quoted text clipped - 32 lines]
Any suggestion?
Thank you
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top