Two Front Ends, One Back End

[JanetF]

Hello,

I have a back end, but need two different front ends to link to the tables
in the back end. One of the front ends will be used by several users and
they will have user names and passwords to get into it. The other front end
will only be used by me. My question is, will there be problems with two
different front ends linking to the same tables, especially if one front end
has security and the other does not?

thanks,
Janet

 

[Jerry Whittle]

I've created different FE's linked to the same BE before like different FE's
for the real workers and another FE for management. No problem.

However your security requirement could throw a wrench into the works. If
you have the BE password secured, your FE will have to link through the
password. If you have the BE with user level security, that could be even
more problems. If you don't have the BE secured at all, no problem EXCEPT why
have the other FE secured at all?

 

[JanetF]

Hi Jerry,

I was probably not clear enough. For one thing, I've only created user
security for one database so far). I have one back end and two front ends.
One front end has to have user level security. The other front end is a
separate mdb file, but linking to the same back end. It will be used by only
me. But I guess the security is really on the back end, not the individual
front ends. Can I use the same mdw and have both of the front ends going
through it?

thanks,
Janet

 

[David Cox]

Yes. You can assign different rights to different roles.

You might want to protect the front end to protect your code, but really you
should be protecting the back end too so that nobody can do anything to your
back end that your front end does not allow, and your front end can monitor
that activity.

 

[JanetF]

Okay, thanks for your help!

Yes. You can assign different rights to different roles.

You might want to protect the front end to protect your code, but really you
should be protecting the back end too so that nobody can do anything to your
back end that your front end does not allow, and your front end can monitor
that activity.

 

[aaron.kempf]

you dont need 2 frontends and 1 backend.

you need 2 Access Data Project files and one SQL Server database.

MDB is for babies.

Spit on people that still use it; they are single-handedly responsible
for half of the identity theft in the world.

ADP is bigger, better, faster and easier development.
MDB is for fat and lazy idiots.

-Aaron
ADP nationalist.