multiple users on one database

  • Thread starter Thread starter Linda
  • Start date Start date
L

Linda

Hello,

Is it possible to have multiple users update a database? We have a need to
make changes from multiple locations. The database is located on a 2000 NT
server. It is a very very flat database...one table with multiple fields.

Thanks,

Linda
 
You'll find that remote connections are very slow, whilke a LAN is just
fine. One thing you can do if you have XP workstations is to use terminal
service to connect to the database. If you do that, the speed will be
acceptable. In any case, you need to split the database. Put all the forms,
queries, reports, code, etc. in a front-end on each workstation and link to
the table on the backend database which is located on the server. If using
terminal services, make a folder for each user and put their own copy of the
database in it. Failing to split the database can result in corruption.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
 
I don't think we can do that. We all have to work from our designated
network drives. Each user has an H drive, and the database is on the M
drive which all users can access. Could I split the database and have it on
the network drives instead of the local machine? No one can access the C
drive. We also do not have Windows XP...only Windows 2000 and Office 2000.

Thanks,
Linda
 
Hello,

Is it possible to have multiple users update a database? We have a need to
make changes from multiple locations. The database is located on a 2000 NT
server. It is a very very flat database...one table with multiple fields.

Thanks,

Linda
Click to expand...

Are these multiple places on a solid, fast, local LAN? In that case,
yes; use the Database Splitter Wizard to store the tables on a shared
drive, and give each user a copy of the "frontend" .mdb file (with the
forms, queries, reports and so on), ideally to be run from their own
machine.

If, however, the multiple locations are on a Wide Area Network, be
aware that Access is not ideal for your situation: databases linked
over a WAN will be slow and extremely prone to corruption.
 
Are these multiple places on a solid, fast, local LAN? In that case,
yes; use the Database Splitter Wizard to store the tables on a shared
drive, and give each user a copy of the "frontend" .mdb file (with the
forms, queries, reports and so on), ideally to be run from their own
machine.

If, however, the multiple locations are on a Wide Area Network, be
aware that Access is not ideal for your situation: databases linked
over a WAN will be slow and extremely prone to corruption.
Click to expand...

I don't know if it's a LAN or WAN. I work in a large hospital with many
computers. Everyone's PC is locked to the point that we can't even create a
shortcut without having the IS dept come and do it. There are no files
saved to the C drive. My Documents is pointing to an H drive (which is
personal to that user) and everyone logs on to access the items they have
permissions to. There are 2 network drives that can be shared. The M drive
is our local hospital's shared drive and only employees from our hospital
can access that one. The N drive where this database is located is a drive
that all 3 or our hospitals can share. We have been using it for over a
year with no problems but only using one PC at a time to open it.


Linda
 
I don't know if it's a LAN or WAN. I work in a large hospital with many
computers. Everyone's PC is locked to the point that we can't even create a
shortcut without having the IS dept come and do it. There are no files
saved to the C drive. My Documents is pointing to an H drive (which is
personal to that user) and everyone logs on to access the items they have
permissions to. There are 2 network drives that can be shared. The M drive
is our local hospital's shared drive and only employees from our hospital
can access that one. The N drive where this database is located is a drive
that all 3 or our hospitals can share. We have been using it for over a
year with no problems but only using one PC at a time to open it.
Click to expand...

If it's three hospitals at different locations, it's a WAN.

I would suggest (as the least bad of several unappetizing options)
trying to persuade IS to split the database; install the 'backend' on
a shared folder on the N drive; and installing a separate folder with
a separate frontend database for each database user on that user's H
drive (which I'm hoping is physically on the same computer or the same
fast network as the N drive).

A better solution may be to use Citrix or Microsoft Terminal Server to
connect to an Access instance on a machine local to the N drive.
 
John Vinson said:
If it's three hospitals at different locations, it's a WAN.

I would suggest (as the least bad of several unappetizing options)
trying to persuade IS to split the database; install the 'backend' on
a shared folder on the N drive; and installing a separate folder with
a separate frontend database for each database user on that user's H
drive (which I'm hoping is physically on the same computer or the same
fast network as the N drive).

A better solution may be to use Citrix or Microsoft Terminal Server to
connect to an Access instance on a machine local to the N drive.
Click to expand...

I have a terminal Server account but the other people don't. There are
about 80 people who would be updating the database. Only 8-10 per day and
they each have a different assignment. They would be responsible to only
update the treatments for their floor. The Supervisor prints out a report
at the beginning of the shift and makes the assignment out. I wonder if I
could have a separate form and table for each work area then just have
queries and reports in another folder of the N drive. Only one person would
be accessing that file at a time. Would that work?

I can think of a huge problem though. Most of these users are extremely
computer literate and I am pretty limited in my ability with access. Even
the people who are using this database each day don't understand file
structure and they need help when they log onto a new PC and don't have the
shortcut in the access Open File dialog box....as shortcuts are stored
locally. I am going to have to brainstorm a bit today....

Thanks
 
Linda said:
I have a terminal Server account but the other people don't. There are
about 80 people who would be updating the database. Only 8-10 per day and
they each have a different assignment. They would be responsible to only
update the treatments for their floor. The Supervisor prints out a report
at the beginning of the shift and makes the assignment out. I wonder if I
could have a separate form and table for each work area then just have
queries and reports in another folder of the N drive. Only one person would
be accessing that file at a time. Would that work?

I can think of a huge problem though. Most of these users are extremely
computer literate and I am pretty limited in my ability with access. Even
the people who are using this database each day don't understand file
structure and they need help when they log onto a new PC and don't have the
shortcut in the access Open File dialog box....as shortcuts are stored
locally. I am going to have to brainstorm a bit today....

Thanks
Click to expand...

That is computer illiterate!
 
Back
Top