Compiled Runtime Database needs new users

  • Thread starter Thread starter mcarlyle via AccessMonster.com
  • Start date Start date
M

mcarlyle via AccessMonster.com

I have a FE/BE database. Everytime I need to add new users I have to go into
the wizard and add the new user and then recompile and redeploy the FE of the
database. Before I made it a runtime i could just update the security and
it would look on the server at the file and be ok.. .now that it is a runtime
it goes to the file that is packaged with the FE runtime. How do I edit that
file that is packaged on the computers? Is that even possible?

Can I compile the program but have it use the security file on the server
still? If so how do I do that? Durring the package process it asks for the
security file and I choose the one on the server but it seems to package it
with the FE.

Thanks in advance for the help.
 
mcarlyle via AccessMonster.com said:
I have a FE/BE database. Everytime I need to add new users I have to go
into
the wizard and add the new user and then recompile and redeploy the FE of
the
database. Before I made it a runtime i could just update the security
and
it would look on the server at the file and be ok.. .now that it is a
runtime
it goes to the file that is packaged with the FE runtime. How do I edit
that
file that is packaged on the computers? Is that even possible?

Can I compile the program but have it use the security file on the server
still? If so how do I do that? Durring the package process it asks for
the
security file and I choose the one on the server but it seems to package
it
with the FE.

Thanks in advance for the help.
Click to expand...


If you have set up security properly, you might have created a number of
standard groups such as ReadOnlyUsers, FullDataUsers, Developers, etc. You
then allocate permissions to the group as a whole and add users to the
group. If you then need to add a new user at a later date, you can do this
easily without affecting the front end and without any need to change any
permissions.
You could build your front end with an AddUser button - in this way you can
simplify the process for your end users, but the simplest way might be for
you to briefly join the workgroup on the server, add the user and allocate
him to one or more groups. Re-join your original workgroup and you're done.
 
The security workgroup is a database, just like any other. If you know
what database is being used, you can add new records to it.

When you package a security workgroup with your runtime application,
what is the name of the security workgroup file? Where is it installed to?

Would you rather have your application use a shared workgroup on
the network somewhere? If so, you probably should ask the question
in microsoft.public.access - people here in security are less likely to
know the answer to installation questions.

(david)
 
Back
Top