Multiple backends to one front end

[Lars Brownie]

For authorisation reasons I need to split my database into 2 backends (with
one frontend) residing in 2 different folders. For one folder only few
employees are authorised in the AD. Fort the other folder authorisations all
employees are authorised.
For the employees who have to access both backends, is it safe to link their
frontend to both of the backends or should I use 2 frontends?

Thanks, Lars

 

[Ken Sheridan]

I see no reason why you shouldn't link to both from a single front end for
the relevant users. One thing you won't be able to do of course is enforce
referential integrity between tables in the separate back ends, so you might
need to incorporate some validation in the front end to prevent
inconsistencies arising

Ken Sheridan
Stafford, England

 

[Tony Toews [MVP]]

For authorisation reasons I need to split my database into 2 backends (with
one frontend) residing in 2 different folders. For one folder only few
employees are authorised in the AD. Fort the other folder authorisations all
employees are authorised.
For the employees who have to access both backends, is it safe to link their
frontend to both of the backends or should I use 2 frontends?

Yes, you can safely link the FE to both backends. However for those
who don't have access to the more secure BE you may want to remove
those table links as performance may suffer drastically even though
you aren't using those tables. Try it and see if this is a problem
first though.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Lars Brownie]

Thanks to both. I'll check out the performance.
Lars