|
|
|
date: Sat, 22 Mar 2008 03:49:57 +0800,
group: microsoft.public.access.multiuser
back
Multiuser/Multiple Backends w/1 frontend
This is a question that fits into what I had seen another user post and I
really need to know how to do it. I am building an application that
requires 4 backends and a login screen. All the backends are exactly the
same (except for the data). I need to know how to allow a user to pick
their name and enter their password and select "which" backend database they
wish to open.
This is for the medical community and the reason for the "multi" backends is
to cover regions...North, South, East..etc...so they cannot go into 1
backend. The user that I was reading about (partial message below), sounds
like they have a similar project and if they could show me how to do it, or
anyone out there, it would be greatly appreciated.
I started the program in Access 2000, but since have upgraded to Access 2007.
A solution for either would be ok, as I could adapt to either.
Thank you very much in advance,
Joseph Ritsko
Jrenter2@charter.net
The post below is portions from the user I was reading about that has a
similar situation.
"A question about multiple backend performance"
"I have built a multi-user Access 2002 database over the last 10 years for a
client. The application is split into 1 frontend and 5 backends: The front
end is on each client."
Patrick
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Patrick Jackman
Vancouver, BC
604-874-5774
url:http://www.ureader.com/gp/1061-1.aspx
date: Sat, 22 Mar 2008 03:49:57 +0800
author: Joseph Ritsko
Re: Multiuser/Multiple Backends w/1 frontend
I would discourage you from building 4 identical backends. My application's
backends all hold different information.
You might consider instead having Region be an attribute of one of the
tables at the top of your hierarchy and filtering what various users see
based on their security group membership.
Patrick.
"Joseph Ritsko" wrote in message
news:ea9a587ba9ee412fa4271b7a4ca82553@newspe.com...
This is a question that fits into what I had seen another user post and I
really need to know how to do it. I am building an application that
requires 4 backends and a login screen. All the backends are exactly the
same (except for the data). I need to know how to allow a user to pick
their name and enter their password and select "which" backend database they
wish to open.
This is for the medical community and the reason for the "multi" backends is
to cover regions...North, South, East..etc...so they cannot go into 1
backend. The user that I was reading about (partial message below), sounds
like they have a similar project and if they could show me how to do it, or
anyone out there, it would be greatly appreciated.
I started the program in Access 2000, but since have upgraded to Access
2007.
A solution for either would be ok, as I could adapt to either.
Thank you very much in advance,
Joseph Ritsko
Jrenter2@charter.net
The post below is portions from the user I was reading about that has a
similar situation.
"A question about multiple backend performance"
"I have built a multi-user Access 2002 database over the last 10 years for a
client. The application is split into 1 frontend and 5 backends: The front
end is on each client."
Patrick
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Patrick Jackman
Vancouver, BC
604-874-5774
url:http://www.ureader.com/gp/1061-1.aspx
date: Fri, 21 Mar 2008 16:06:31 -0700
author: Patrick Jackman
Re: Multiuser/Multiple Backends w/1 frontend
While I agree with others about the necessity for multiple backends, I have a feeling you don't have much choice in the matter.
To answer your question, you can use the example at
http://www.access.qbuilt.com/html/custom_login.html
to create the custom login form. You'd just need to add an option group for the user to select which backend they want to connect to.
--
Joan Wild
Microsoft Access MVP
"Joseph Ritsko" wrote in message news:ea9a587ba9ee412fa4271b7a4ca82553@newspe.com...
> This is a question that fits into what I had seen another user post and I
> really need to know how to do it. I am building an application that
> requires 4 backends and a login screen. All the backends are exactly the
> same (except for the data). I need to know how to allow a user to pick
> their name and enter their password and select "which" backend database they
> wish to open.
>
> This is for the medical community and the reason for the "multi" backends is
> to cover regions...North, South, East..etc...so they cannot go into 1
> backend. The user that I was reading about (partial message below), sounds
> like they have a similar project and if they could show me how to do it, or
> anyone out there, it would be greatly appreciated.
>
> I started the program in Access 2000, but since have upgraded to Access 2007.
> A solution for either would be ok, as I could adapt to either.
>
> Thank you very much in advance,
>
> Joseph Ritsko
> Jrenter2@charter.net
>
>
> The post below is portions from the user I was reading about that has a
> similar situation.
>
> "A question about multiple backend performance"
>
> "I have built a multi-user Access 2002 database over the last 10 years for a
> client. The application is split into 1 frontend and 5 backends: The front
> end is on each client."
>
> Patrick
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Patrick Jackman
> Vancouver, BC
> 604-874-5774
>
> url:http://www.ureader.com/gp/1061-1.aspx
date: Mon, 24 Mar 2008 08:40:29 -0400
author: Joan Wild
Re: Multiuser/Multiple Backends w/1 frontend
Patrick, the backends would hold different information, they would just all
look the same. See, each region has facilities that have medical equipment
tested. These results have to be put into their respective areas. So, if a
technician comes back from testing and goes to input their results for the
day, they would be able to Login with their name and then be able to choose
from a dropdown list which area they went to for testing and start putting
their information in.
I know how to do the login part, but I don't know how to allow the user to
choose from the different backends. The backends are all named differently
according to their respective area.
At this time, all I have is 3 boxes on my screen, one for "Account" (region),
one for Username and one for Password.
I hope you can see what I am trying to do now and can give some assistance.
Thanks,
Joe
url:http://www.ureader.com/msg/1061845.aspx
date: Mon, 24 Mar 2008 21:29:11 +0800
author: Joseph Ritsko
Re: Multiuser/Multiple Backends w/1 frontend
Hi -
I have to disagree with those who say *no* to multiple back-end databases.
There are times when it makes perfect sense. I have several applications
which deal with job studies. While the data structure for each study is
identical, the data is not, and the studies are not really related to each
other.
In each application, the Windows Common Dialog allows users to select the
study database they want to work with, the application deletes any existing
links, and creates new links to the tables in the selected database. It's
easy enough to do, but requires some VBA programming.
So, Joe, if you are absolutely sure that there will never be a requirement to
merge or rollup data from all the regions, then by all means use as many
backend databases as you need - other than setting up the links, the FE
should require few changes.
John
Patrick Jackman wrote:
>You appear to be getting lots of good ideas here Joe.
>
>I hope you've given up the multiple backend idea.
>
>Patrick.
>
>hi hi.. Pls let me join this discussion! how about the user table ? one user
>can have access to only one region ? then how about creating new field as
>region in user table then let them go to their respective region? u can
>redirect them to their repective region by chking the region field in
>usertable ?
>
>Tony Toews [MVP] wrote:
>>>Patrick, the backends would hold different information, they would just
>>>all
>[quoted text clipped - 8 lines]
>>
>>Tony
>
--
John Goddard
Ottawa, ON Canada
jrgoddard at cyberus dot ca
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-multiuser/200803/1
date: Fri, 28 Mar 2008 17:10:09 GMT
author: J_Goddard via AccessMonster.com u37558@uwe
Re: Multiuser/Multiple Backends w/1 frontend
Well, Patrick, yes, there are many good ideas here. Joan, I looked at that
link and that will help., John, while my application is not about job studies,
the backends are identical in design, but the data is all different. I will
never have to combine reports, data or anything between the backends because
the data will be all different.
Let me explain exactly what this is....I may not have done this in the
beginning and I apologize. I am doing this project for my old boss in
Florida. He owns a biomedical repair facility. He has 2 technicians that
work for him. What they do is go out to all parts of the state and do
testing and calibration on various pieces of medical equipment at different
facilities, (Dr. Offices, Surgery Centers...etc). When they come back with
the information they upload the facility into the system and then a report
for that faciltiy is sent to the client. One day they could be testing on
the west coast, the next day on the east. If they need to generate a work
order or see if a piece of equipment exists, they log into the system and
choose which account they want to go to.
The accounts will be set up as West Coast, East Coast, North, South. Within
each account, they all hold different clients, equipment..work orders, etc.
What I have now is a Login screen that asks for the user name and password
and a combo box (thanks Joan)..that shows West Coast, East Coast, North,
South.
What I need to be able to do is after they choose the account they want and
they put in their username and password and hit the login button...it relinks
and opens the main form of that particular account. When they are finished
and hit the logout button for that account...it removes the links and goes
back to the main login form and is ready for someone else to log into the
program.
If I could get this accomplished, life for me would be greater...LOL.... I
hope I was able to clarify a bit of what I am doing.
Thanks for everyones replies. I am very glad I have found this discussion
group. I have learned so much thus far to help me in different areas.
J_Goddard wrote:
>Hi -
>
>I have to disagree with those who say *no* to multiple back-end databases.
>There are times when it makes perfect sense. I have several applications
>which deal with job studies. While the data structure for each study is
>identical, the data is not, and the studies are not really related to each
>other.
>
>In each application, the Windows Common Dialog allows users to select the
>study database they want to work with, the application deletes any existing
>links, and creates new links to the tables in the selected database. It's
>easy enough to do, but requires some VBA programming.
>
>So, Joe, if you are absolutely sure that there will never be a requirement to
>merge or rollup data from all the regions, then by all means use as many
>backend databases as you need - other than setting up the links, the FE
>should require few changes.
>
>John
>
>>You appear to be getting lots of good ideas here Joe.
>>
>[quoted text clipped - 14 lines]
>>>
>>>Tony
>
date: Fri, 04 Apr 2008 14:57:41 GMT
author: Joe Ritsko u42692@uwe
|
|
