Multi-user database with common front-end

31 Oct 2005 6:11 PM

KarenH

I have a database that requires two separate groups of users -- one will have
read-only access, the others will be able to change data. Furthermore, the
forms in the front end will display differently depending upon the user group
of the person signing in. However, I cannot use a shortcut or individual
front-end on the desktop because of concerns over updating for changes. Can
this be done? Can I have separate users without a separate front-end? There
will be as many as 15 people hitting the application at one time. I
currently have it keying off the CurrentUser and the group they are in, but
if multiple people are hitting one common front end on a server, I'm thinking
the currentuser will only be the first person to sign in.

??

31 Oct 2005 8:09 PM

Joan Wild

KarenH wrote:

> I have a database that requires two separate groups of users -- one
> will have read-only access, the others will be able to change data.
> Furthermore, the forms in the front end will display differently
> depending upon the user group of the person signing in. However, I
> cannot use a shortcut or individual front-end on the desktop because
> of concerns over updating for changes. Can this be done?

You can implement Access userlevel security to accomplish this.

> Can I have
> separate users without a separate front-end? There will be as many
> as 15 people hitting the application at one time. I currently have
> it keying off the CurrentUser and the group they are in

Oh, so you have implemented security in Access then?

>, but if
> multiple people are hitting one common front end on a server, I'm
> thinking the currentuser will only be the first person to sign in.

This is only one reason to split the database. Put just the backend on the
server and give each user a copy of the frontend on their PC. If you need
to redeploy an updated frontend to users you can use a utility like that at
Tony Toews' site to automate this.
http://www.granite.ab.ca/access/autofe.htm

--
Joan Wild
Microsoft Access MVP

31 Oct 2005 8:29 PM

KarenH

Yes, I did implement the user-level security, and put a copy of the front end
on each of the users desktop, but I have to get rid of that, they want
everyone hitting one copy of it -- so I am trying to figure out if the
user-level security that I put in is even going to work. Or if, when my code
hits a reference to the "current user", it will just reflect the first person
that logged into it.

Show quoteHide quote

"Joan Wild" wrote:

> KarenH wrote:
> > I have a database that requires two separate groups of users -- one
> > will have read-only access, the others will be able to change data.
> > Furthermore, the forms in the front end will display differently
> > depending upon the user group of the person signing in. However, I
> > cannot use a shortcut or individual front-end on the desktop because
> > of concerns over updating for changes. Can this be done?
>
> You can implement Access userlevel security to accomplish this.
>
> > Can I have
> > separate users without a separate front-end? There will be as many
> > as 15 people hitting the application at one time. I currently have
> > it keying off the CurrentUser and the group they are in
>
> Oh, so you have implemented security in Access then?
>
> >, but if
> > multiple people are hitting one common front end on a server, I'm
> > thinking the currentuser will only be the first person to sign in.
>
> This is only one reason to split the database. Put just the backend on the
> server and give each user a copy of the frontend on their PC. If you need
> to redeploy an updated frontend to users you can use a utility like that at
> Tony Toews' site to automate this.
> http://www.granite.ab.ca/access/autofe.htm
>
> --
> Joan Wild
> Microsoft Access MVP
>
>
>
>

31 Oct 2005 8:58 PM

Joan Wild

KarenH wrote:

> Yes, I did implement the user-level security, and put a copy of the
> front end on each of the users desktop, but I have to get rid of
> that, they want everyone hitting one copy of it

You are definitely going to corrupt the database if you go this route.

--
Joan Wild
Microsoft Access MVP

1 Nov 2005 8:50 AM

Keith

"KarenH" <Kar***@discussions.microsoft.com> wrote in message
news:6F17A030-5666-47DB-AD2D-C64D2E24C6F8@microsoft.com...
> I have to get rid of that, they want
> everyone hitting one copy of it

"They" being management who don't have a clue what they're doing? Been
there. You need to explain to them the danger of data corruption if "their"
method is adopted. "They" shouldn't be looking in the engine compartment in
the first place.

Regards,
Keith.
www.keithwilby.com