Hello,
I have a split application where there is a common front end that accesses
multiple sets of backend tables. When the user logs in they select the back
end they want to work with and the proper tables are linked. The front end is
on the server and each user has a shortcut to the mdb on their desktop.
What was a single user system will now be multiple users. What is happining
is, a user logs in and selects the backend tables they want. Then when a
second user logs in and selects a different back end the first user is
accessing the second user's back end selection.
Is there a way to have each user share the common front end but when they
open the application they use their own copy can work on different back end
databases?
Thank You

Each user should have his/her own copy of the front-end, ideally on his/her
hard drive.

Sharing front-ends is a leading cause of database corruption.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"Chuck" <(E-Mail Removed)> wrote in message
news:04F169AD-E0E0-40D3-AA86-(E-Mail Removed)...
> Hello,
> I have a split application where there is a common front end that accesses
> multiple sets of backend tables. When the user logs in they select the
> back
> end they want to work with and the proper tables are linked. The front end
> is
> on the server and each user has a shortcut to the mdb on their desktop.
> What was a single user system will now be multiple users. What is
> happining
> is, a user logs in and selects the backend tables they want. Then when a
> second user logs in and selects a different back end the first user is
> accessing the second user's back end selection.
> Is there a way to have each user share the common front end but when they
> open the application they use their own copy can work on different back
> end
> databases?
> Thank You

I would put the tables on the server and the front ends on the C drive of
each users computer. ???

"Chuck" wrote:

> Hello,
> I have a split application where there is a common front end that accesses
> multiple sets of backend tables. When the user logs in they select the back
> end they want to work with and the proper tables are linked. The front end is
> on the server and each user has a shortcut to the mdb on their desktop.
> What was a single user system will now be multiple users. What is happining
> is, a user logs in and selects the backend tables they want. Then when a
> second user logs in and selects a different back end the first user is
> accessing the second user's back end selection.
> Is there a way to have each user share the common front end but when they
> open the application they use their own copy can work on different back end
> databases?
> Thank You

Doug and Paul,
Looks like that's the answer.
Thanks for the quick responces.
Chuck

"Paul.S" wrote:

> I would put the tables on the server and the front ends on the C drive of
> each users computer. ???
>
> "Chuck" wrote:
>
> > Hello,
> > I have a split application where there is a common front end that accesses
> > multiple sets of backend tables. When the user logs in they select the back
> > end they want to work with and the proper tables are linked. The front end is
> > on the server and each user has a shortcut to the mdb on their desktop.
> > What was a single user system will now be multiple users. What is happining
> > is, a user logs in and selects the backend tables they want. Then when a
> > second user logs in and selects a different back end the first user is
> > accessing the second user's back end selection.
> > Is there a way to have each user share the common front end but when they
> > open the application they use their own copy can work on different back end
> > databases?
> > Thank You

Chuck <(E-Mail Removed)> wrote:

>Is there a way to have each user share the common front end but when they
>open the application they use their own copy can work on different back end
>databases?

You've already got the answer. But as an additional tip see the free
Auto FE Updater utility at http://www.granite.ab.ca/access/autofe.htm
at my website to keep the FE on each PC up to date.

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/

I hope that I have posted this in the right area. I have been looking
forever to find an example of what Chuck has written here. I was wondering
if someone could point me in the right direction.

I am using Access 2007 and am needing an example, sample, etc..of how to
allow a user to log in and select the backend they want to work with and have
the proper tables linked. Then if they log out of that account (backend) it
unlinks them so they can choose another account (backend).

Any and ALL help would be greatly appreciated.

Thanks,

Joe


"Chuck" wrote:

> Hello,
> I have a split application where there is a common front end that accesses
> multiple sets of backend tables. When the user logs in they select the back
> end they want to work with and the proper tables are linked. The front end is
> on the server and each user has a shortcut to the mdb on their desktop.
> What was a single user system will now be multiple users. What is happining
> is, a user logs in and selects the backend tables they want. Then when a
> second user logs in and selects a different back end the first user is
> accessing the second user's back end selection.
> Is there a way to have each user share the common front end but when they
> open the application they use their own copy can work on different back end
> databases?
> Thank You